The following notes describe updates to AppDynamics Application Performance Monitoring, or the Language Agents, which gives you end-to-end visibility into the performance of your applications.
If an artifact has been updated, the version number of the updated artifact and its availability date are listed below. The version number corresponds to that shown on the download portal (http://download.appdynamics.com).
The most recent releases appear at the top of the page.
For information on agent and Controller compatibility, and updates to individual AppDynamics Language Agents, see the following pages:
- 4.5.x Java Agent Notes
- 4.5.x .NET Agent Notes
- 4.5.x Node.js Agent Notes
- 4.5.x PHP Agent Notes
- 4.5.x Python Agent Notes
- 4.5.x Java Serverless Tracer Notes
- 4.5.x Node.js Serverless Tracer Notes
- 4.5.x Apache Web Server Agent Notes
- 4.5.x C/C++ SDK Notes
- 4.5.x Go Language Agent Notes
- 4.5.x IBM Integration Bus Agent Notes
For updates to new decoupled agents developed by partners or other third parties, see the following pages:
April 22, 2019
Role-based Access Control for Business Journeys and Experience Level Management
- Application Analytics now enforces role-based access control (RBAC) for business journeys and experience level management (XLM). Upon rollout of RBAC, only the analytics administrator has access to business journeys and XLM. All other users see a warning in the controller UI stating that access is denied for any action or query within business journeys and XLM.
- The analytics administrator must grant permission on an individual basis to all users by creating new roles. Roles should include all applicable access for each user, both for business journeys and XLM. RBAC consists of three categories:
- General - provides feature level access to business journeys and/or XLM. In addition to feature level access, search and event access are required to query, search, or create business journeys and XLM.
- Searches - provides access to query data, which enables users to perform and save searches on business journey or XLM events.
- Events - provides access to events type(s) and source(s). A user can only access the exact event type(s) and source(s) granted in the role. This is required in order to create a business journey or XLM definition or to access and create reports for particular sources.
- Business journey events cannot be accessed through the Custom Events API.
- No data is lost in the transition phase. RBAC restricts all users from accessing business journeys and XLM at the outset. However, if your analytics admin grants the exact access required for previously saved reports you will be able to access the report again as if the access had never been denied.
Not able to edit Thread Dump Collection Interval
Setting PHP MVC custom match rules in the Controller UI results in exceptions when the backend creates the rule for the agent AND custom STRUTS rule (Java) to use
Information Point created from Snapshot drill down has blank class and method names
Clicking "Node Dashboard > Grid view > Node" results in the error "Invalid unresolved backend call id :xxx"
Unable to persist segment number for Custom Service Endpoint with payload splitting
An exception occurs while creating or editing a PHP MVC custom match rule in Java
February 25, 2019
|Getting "500 Internal exception" when trying to close the criteria Performance data|
|Sort by count is broken on All Other Traffic modal|
|Collection interval for getting Thread Dumps is broken|
February 11, 2019
- ADQL now offers data conversion functions. You can use data conversion functions to correct erroneous data types, or format data types to enable mathematical or indexing functions.
- You can now determine field type for HTTP Request and Method Invocation Data Collectors with transaction analytics data type conversion.
|APPS_ALL_DASHBOARD screen, View Option does not persist|
|Sorting by tier name does not work on the Exception rate page|
|Logger name typo (when collecting agent debug logs for Java)|
|Unable to render "App Server Agent Configuration" for all nodes|
Error 404 on UI when trying to disable an agent
|Stale backend purger not working|
|Execution time in transaction snapshots is always showing zero|
|Agent's backward compatibility broken|
December 21, 2018
|Database health rules are not evaluating with an external user who has default Account Owner and Administrator roles|
|Baseline of type None needs 1 day data|
|Number of nodes value is wrong in tiers and node dashboard|
|Replace Correlation Analysis|
|Not able to edit Thread Dump Collection Interval|
November 19, 2018
There are new REST APIs to export and import transaction detection rules in Config 2.0. See Configuration Import and Export API for more information.
|REST API to import transaction detection is not working|
|Remote Services does not select the correct elements|
|Navigating to the "Business Transaction" tab from the "Flow Map" edge causes an HTTP 500 Error|
|Not able to create applications and register new nodes after upgrading to 4.5.1 on on-prem Controllers|
|Sorting is done incorrectly for an Error count|
|Automatic "Service Endpoint Detection" cannot be configured at the application level|
|"All Apps" page doesn't load for one day because the maximum number of return points was exceeded|
|Remote Services does not select the correct elements|
|REST API to import transaction detection not working|
October 15, 2018
Deprecation and End of Life (EOL) Notices
- The Cloud Auto-Scaling functionality has been removed. Once a Controller is upgraded to 4.5.2, Cloud Auto-Scaling will no longer be available in the UI and the functionality will no longer work.
September 5, 2018
- The Controller no longer records zeros for missing APM agent metrics. The removal of the zero-fill method will help with scalability and consistent handling of zero values.
|BT lockdown flag not propagated to agent|
|Add repetitive logger for incorrect SEP registration error messages in server.log|
|Fix to properly enable/disable agent from the agent status UI screen|
|Upgrade scripts for Axon (v2.x and 3.x) framework|
|Unable to save Python Error Detection Configuration|
July 11, 2018
Language Agent Backward Compatibility
Starting in release 4.5, AppDynamics language agents are backward-compatible with any 4.4.1 or higher Controller. Thus you can upgrade your language agents – and take advantage of the latest agent-side enhancements, features, and bug fixes – without upgrading your 4.4 Controller. The following table outlines the Controller and language agent releases that are compatible.
|Controller Release||Language Agent Release||Notes|
|4.4.1+||4.1+||4.4.1 and newer Controllers can accept connections from newer agents.|
|4.3.x||4.1.x – 4.3.x||4.3.x Controllers cannot accept connections from newer agents.|
|4.2.x||4.1.x – 4.2.x||Agents older than 4.3 are no longer supported, and agents older than 4.1 are no longer guaranteed to connect to a Controller.|
Backward compatibility is supported on the following agents starting in Release 4.5:
- Go SDK
You can now drill down into federation applications. This allows you to display incoming calls from the upstream federated application.
A new Create Events permission has been created.
Snapshot Waterfall Viewer
- The Waterfall View within the snapshot viewer has been comprehensively enhanced. It now shows time spent in uninstrumented backend systems as well as inactive threads within instrumented nodes, and also shows the relationships between the segments. For asynchronous Business Transactions, it also labels the threads where the Business Transaction begins and ends.
|User without CREATE_APPLICATION permission is not able to archive events, and delete events has missing permission check|
|Config Export REST call throws an exception and returns 500 Internal Server Error|
|Error message shown when upstream BT's of masked transactions are excluded|
|Multiple tiers in the metric browser|
|Agent reports snapshots for deleted BTs|
|DB & Remote Service Calls: missing comma in column Total Time|
|NPE at BTFlowMapServiceImpl.computeBTFlowMapTopologyAndFetchMetricDataInternal() due to MetricQueryManagerBean.getMetricNode() returns null|
|Internal Server Errors when viewing snapshots|
|UI display historical nodes|
|Improve logic of node purger|
|UI shows duplicate queries in the Potential issues section|
|Improve getProcessSnapshotDataByGuid performance|
|Tier & Node list not fully populating|
|Snapshot Waterfall has the wrong sort order|
|Tier and Node showing null for JVM restart time|
|Tiers and Nodes page: missing tier count top right corner|
|IIS App Pools page gets stuck under Tiers & Nodes|
|Copy REST URL in metric browser broken|
|Error response after copying/pasting REST URL from Metric Browser|
- Business transaction retention settings are not affected by the
business.transaction.retention.periodvalue in the Admin Console (available with On-Prem deployments only).
- For JMX functionality to work, set a Currently monitored statistic set to an option other than None in IBM WebSphere.