On this page:
The first generally available 4.5.x release is 4.5.0.<build-number>.
The release notes are inclusive. All updates since 4.5.0 are noted in the 4.5 Release Notes. The Product Announcements and Alerts page lists versions, along with release dates, across product versions.
This documentation reflects AppDynamics Application Intelligence Platform version 4.5.x. Changes between minor versions are noted in the release notes and indicated in-place in the documentation where applicable.
See the relevant page for the component you want to install or upgrade.
|Platform Requirements||Agent Requirements|
The following updates apply to the common components of the AppDynamics App iQ Platform, including changes to the cross-product elements of the Controller UI.
Application Performance Management
App iQ .NET Core for Linux SDK
The .NET Core for Linux SDK lets you monitor the performance of .NET Core applications running on Linux with App iQ.
The SDK supports the following:
Data Collection Dashboard
Custom Dashboard Viewer permissions
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.
Backward compatibility is supported on the following agents starting in Release 4.5:
Snapshot Waterfall Viewer
Java Agent Enhancements
.NET Agent Enhancements
IBM Integration Bus Agent Enhancements
Important Note about Changes in Dynamic Monitoring from Previous Releases
Standalone Machine Agent Enhancements
Server Visibility Enhancements
Network Visibility Enhancements
Standalone Machine Agent Known Issues
Server Visibility Known Issues
Docker Visibility Known Issues
Network Visibility Known Issues
Enhancements and Updates
Experience Level Management (XLM)
You can now specify files to exclude from ingestion, by defining a glob pattern of file paths to the blacklist.
Upgrading the Analytics Agent
If you are running the Analytics Agent as a standalone binary, see this topic: Upgrade Analytics Agent.
If you are running the Analytics Agent through the Standalone Machine Agent, See Upgrade the Standalone Machine Agent for instructions.
If you have been collecting log analytics data:
Field Names for Data Collectors
In versions prior to 4.3, Analytics used the actual HTTP parameter name to display the fields collected by Data Collectors. Beginning in 4.3, Analytics is using the configured display name for such fields.
When you upgrade to agents versions 4.3 or above, new HTTP parameter data will appear under the display name. If you had previously configured the display name to be different from the actual parameter name, your historical data and new data collected by the 4.3 or 4.4 agents for a single HTTP parameter will be split between the two field names.
Enabling Transaction Analytics
Beginning with 4.3 agents, you should enable Transaction Analytics exclusively using the Analytics Configuration UI. The Analytics Configuration UI allows for enabling Analytics at the Application level. You should no longer use the deprecated
Version 4.2 and earlier app server agents use the
Although the Analytics Dynamic Service configurations can be directly changed through the application import and the Analytics Dynamic Service import REST API, manipulating the Analytics Dynamic Service configurations through either of those mechanisms only updates the Analytics Dynamic Service configurations and not the corresponding
The following notes describe updates to the AppDynamics on-premises platform, including the Controller, Events Service, and EUM Server components.
Controller / Events Service
Ubuntu version 16 and higher requires the tzdata package in order to install the 4.5 Enterprise Console and Controller.
Controller audit reports do not work immediately after upgrading the controller to 4.5. Audit table migration messages are logged in the server.log file when audit reports are run before completing the audit database table migration process. Try running the audit reports again at least an hour after the upgrade.
You can find this update in the following:
|DBMON-3371||4.5 Controller installation fails without Internet access|
|ECONSOLE-3417||"add_secondary" job fails when primary controller was previously part of a High Availability pair|
|ECONSOLE-3486||High Availability – Incremental Replication is still susceptible to space ID collisions when running on older Linux platforms|
|METADATA-4827||Controller installation/upgrade fails at MDS schema upgrade|
|SYNTH-3558||Synthetic functionality is unavailable due to license-check error on accounts with EUM enabled|
You can find this update in the following:
|BRUM-4085||Controller is unable to download metrics using proxy|
|PLATCPS-4555||Agent availability status constantly changes due to metric cache|
If a 4.5.1 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).