For updates to the Universal Agent, see the following page:
September 17, 2019
The software for this update is available to SaaS-only customers at this time. For those on-premises customers considering upgrading to the latest version, the following describes what has been fixed in the next release.
When a business transaction (BT) that represents the endpoint of a service calls another BT that represents the endpoint of another service, that is a "cross-BT" call. This is typical of One-App-Per-Service architectures, where multiple applications each correspond to a different services and BTs represent service endpoints.
Cross-BT Correlation is a new AppDynamics feature that enables you to inspect cross-BT calls, using the Cross-BT Hovercard in the Application flow map.
The hovercard provides performance data for cross-BT calls, including those that fail to reach their intended targets. This enables you to perform service monitoring, problem isolation, and root cause analysis (RCA) for applications in One-App-Per-Service architectures.
August 26, 2019
- You can now see Application context in the audit report for all the entities, enabling a better understanding of application information at the top level.
- Modifications to Business Transaction config are audited in the context of an Application
- Modifications to Alerts/Health Rules are also audited with Application Name to facilitate a consistent end-user experience
- Application Analytics
Analytics now has a home page. See Application Analytics Notes for more information.
July 31, 2019
- The Tiers & Nodes dashboard by default only shows the tiers and nodes that receiving performance data for the selected timeframe. You can use a filter to view tiers and nodes receiving performance data, not receiving performance data, or all tiers and nodes.
- Whenever a user is deleted from the user list, any custom dashboard that the user has created becomes non-functional with no permissions, and is unable to execute properly. This impacts all associated dashboard-based reports and shares. You can solve this problem using the Recover function.
July 8, 2019
- Application name is added to the entities that are defined in the Controller Audit for OBJECT_CREATED and OBJECT_UPDATED. See Controller Audit Log for more details.
- Flash is disabled by default for the entire Controller UI.
- The Metric Browser also only shows by default the nodes for business applications that are receiving performance data for the selected timeframe. You can also use a filter to view nodes receiving performance data, nodes not receiving performance data, or all nodes.
- AppDynamics enables the monitoring of all containers on the host machine through the sim.docker.monitorAPMContainersOnly property. By default, only containers with APM agents running inside are monitored but this behavior can be changed by setting this property to false.
- You can now set permissions for the Analytics API Key on Connected Devices.
March 25, 2019
- The medium-sized Controller has been certified to run on Amazon Web Services (AWS) with Aurora database support. See Controller System Requirements
- Anomaly detection and root cause analysis, powered by the Cognition Engine, is now generally available for all SaaS customers.
- The pipe '|' or colon ':' can now be used interchangeably for the metric selection to work. See Using Wildcards in Metric Definitions
July 11, 2018
Application Performance Management