On this page:

Your Rating:
7 rates
This topic covers release information for the AppDynamics App iQ Platform versions 4.4.x. In addition to the enhancements and resolved issues described here, the latest 4.4.x release includes enhancements and resolved issues included in certain limited-availability releases, as well as security fixes. 

The first generally available 4.4.x release is, which incorporates fixes to pre-release issues in and

The release notes are inclusive. All updates since are noted in the 4.4.x Release Notes. The Product Announcements and Alerts page lists versions, along with release dates, across product versions. 

The 4.4.x documentation reflects AppDynamics Application Intelligence Platform version 4.4.x. Changes between minor versions are noted in the release notes and indicated in-place in the documentation where applicable.   

AppDynamics App iQ Platform Notes 

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. 


Enterprise Scale

  • Every component of the AppDynamics iQ platform, including the UI, has been enhanced to support 10 million metrics per minute from ingestion, processing, storage, and UI performance perspectives on SaaS implementations of the Controller. The platform also supports 20k agents and 40m registered metrics. This enhancement brings about the following improvements:
    • Controllers can now handle three to four times more agents than before, reducing the number of Controllers required and the total cost of ownership of your AppDynamics installation.

    • Very large applications, which were previously split between multiple Controllers, can be monitored by one Controller, providing a more holistic view of the application.

Simple Search

  • You can now find a tier, node, application, or business transaction by simply clicking the find button on the top of the Controller UI and entering the first few letters of the entity name. Once you have found the entity of interest, you can click it in the list of matching items in the search box to open the flow map for that entity.
    Keep the following details in mind when using the Simple Search feature:
    • The feature supports global search, not contextual search, so it is not limited to one application.
    • The feature does not perform strict contains search. The searched entity is broken down into tokens, and Simple Search supports a “stats with” search within each token.
    • Searches are not case sensitive.
    • You need to have Events Service installed for Simple Search to work since data and indexes are created and stored in it.

Custom Dashboard

  • The look and feel of dashboards has been simplified and improved, especially for the Heap & Garbage Collection dashboard found under the Memory tab of Tiers & Nodes.
  • The Health List widget has been merged with the Health Status widget since both supported similar concepts. The functionality of the new Health Status widget is the same as the old one but with a few improvements. The Health Status widget can support bar, list, and status light circle visuals. The circle supports multiple health rule evaluations, and now has different aggregation displays. Old, existing Health List and Health Status widgets are converted to the new Health Status widget upon upgrade. For more information, see Widgets.

  • You now have more control on how you would like your metric values to be displayed. In the Metric Value widget, you can specify the formatting of metric numbers by abbreviating them, setting a decimal limit, and removing trailing zeros. For more information, see Widgets.

  • For the Time Series Graph widget, selecting “Tier / Node Health - Transaction Performance” as your Metric Category to view infrastructure metrics no longer provides data points since it now correctly corresponds to overall application performance metrics. To see infrastructure metrics, you must change the configuration to “Tier / Node Health - Hardware, JVM, CLR”. For more information, see Widgets.

Universal Agent 

  • The AppDynamics Universal Agent is a deployment tool that automates the tasks of installing, running, and maintaining AppDynamics agents. The Universal Agent runs on Linux and Microsoft Windows systems, and is best used to manage agents in very large deployments. In this release, the Universal Agent adds support for managing the .NET Agent, Analytics Agent (for Transaction Analytics), and Network Agent. For more information, see AppDynamics Universal Agent

User Management

  • You can create and manage users, groups, and roles using RBAC REST APIs. For more information, see RBAC API.

License Management

  • You can manage licenses for Network Visibility on the License page.

Resolved Issues


ALERT-6Action dialog UI freezes when an existing action within an email template is opened, saved, or edited
ALERT-17Deep link URL provided by a custom action linked to an AppServer restart event is broken
ALERT-24Health rule evaluation for a metric with rollup type=CURRENT takes first unit of time in the interval when it should take the last
ALERT-25Health rule fires even when the machine agent availability metric is not reporting due to issue with association
ALERT-32500 error occurs when you try to retrieve Export Actions with invalid application name
ALERT-122Triggering issue with HTTP request actions on SaaS Controller is fixed by enabling logging of HTTP actions to the server log
ALERT-215Health rules trigger false positive alerts due to inaccurate baseline values
ALERT-217Recursive check on metric conditions fixes enforcement issue with the EUM license requirements when creating health rules
ALERT-236No text field present under drop down "Servers/Node matching the following Criteria" for default health rules
ALERT-415HTTPActionPlan double encodes query parameter
ALERT-505Unable to save health rule if Group Count is selected
ALERT-538Incidents remain open even after health rule returns to NORMAL
ALERT-569Potential security issues detected in third-party libraries
ALERT-571Events which trigger actions show actions triggered even if the action is set to disabled
ALERT-589"Disk Usage is too high ..." health rule status does not get evaluated
DASH-582Widget title is overwritten when opened for editing
DASH-952Dashboard with Metric Value widget displays values as "_ _"
PLATCPS‑1095License rule dialog does not filter out removed apps/machines when editing a license rule
RPTSVC-7Absolute layout dashboard now uses the dashboard size to set the content page size
RPTSVC-104Dashboard and Audit Reports do not show current timezone data
UIPLAT-589Settings gear icon is unresponsive for Controllers with custom instance methods
UIPLAT-300License rule name containing "&" is not selectable in the UI

Known Issues

 Universal Agent

  • To use the Universal Agent to deploy the Analytics Agent on Linux, you must use machine-agent mode. Standalone mode is not supported for this use case.

  • Using the auto-Java feature for deployment of the Java Agent with the Universal Agent is not supported on Windows 2008 SP2 32-bit and 64-bit.
  • To install the .NET Agent with the Universal Agent use a local repository for the .NET Agent distribution file. Downloading the .NET Agent from the Controller is not supported.

IBM WebSphere

  • For JMX functionality to work, set a Currently monitored statistic set to an option other than None in IBM WebSphere.

Application Performance Management Notes



Controller Enhancements

  • You can set up a trust called federated friendship between business applications in different accounts on one or more Controllers. When business applications from the friend accounts make entry and exit calls to one another, they show up in flow maps as federated cross application flow.
    Federated cross application flow works with Java and .NET agents that are version 4.4 or later.

  • You can filter business applications from flow maps that show cross application flow. The filter does not apply to applications in other accounts participating in federated cross application flow.

  • In live preview mode, the number of methods and classes that can be returned by an agent are now limit-bounded. The limits are:
    • Maximum number of classes: 1000
    • Maximum number of methods: 300
    For more information on live preview mode, see Custom Match Rule Live Preview.

C/C++ Agent Enhancements

  • You can override the default business transaction start time using the appd_bt_override_start_time_ms method. The default start time is epoch time (January 1, 1970 UTC). For more information, see C/C++ Agent SDK Reference.

Go Agent Enhancements

  • The Logging property in the Config struct lets you configure logging settings, such as where log files are written to and the maximum number of logging files to store on disk. For more information, see Go Agent SDK Reference.

Java Agent Enhancements

  • You can register the spring-mvc-naming-scheme node property to configure naming of Spring MVC requests. See spring-mvc-naming-scheme node in App Agent Node Properties Reference for more information.

  • A new system property, appdynamics.agent.ssl.keymanager.factory.algorithm, let's you set the algorithm pertaining to SSL Mutual Authentication between the Agent and Controller. To use the property, add the option to the JVM startup command, as in the following example:

  • The Java Agent automatically detects Mule ESB HTTP and JMS entry points for versions 3.6, 3.7, 3.8, and 3.9. It also discovers Mule ESB HTTP exit points for the same versions.

  • The agent now supports Java 9. See Java Supported Environments for complete support information.
  • The Java Agent adds support for JMX Metrics for Kafka Broker.
  • The Java Agent adds support for Eclipse Vert.x versions 3.4.1 and 3.4.2.
  • Backend support added for Ning Asynchronous HTTP clients version 1.x (NingAsyncHttpClient) and 2.x (AsyncHttpClient).
  • Previously, with the -Dappdynamics.agent.reuse.nodeName property enabled, the Java Agent wrote log information to a buffer. After registering with the Controller, it wrote the buffered logs to a log directory created upon registration. If registration failed, however, the buffered log messages were lost, making it difficult to troubleshoot startup and registration issues.
    Now, prior to registration, agent logs are written to stdout by default, and you have the additional option of having them written to a log file instead. Writing to a log file enables you to troubleshoot agent startup problems in case registration fails. See Instrument JVMs in a Dynamic Environment for more information.

.NET Agent Enhancements

  • The .NET Micro Agent no longer requires the AppDynamics .NET Agent Coordinator Service. You can install the .NET Micro Agent directly on Azure App Services and Azure Service Fabric.

  • When the .NET Micro Agent is installed on Azure App Services and Azure Service Fabric, it installs the project files to <project_root>/AppDynamics/AppDynamicsConfig.json.
  • The .NET Agent supports Microsoft ASP.NET Core on the full .NET Framework 4.0+ hosted on Kestrel, WebListener, and OWIN. The agent names transactions based upon MVC area, controller, and action by default. See Name MVC Transactions by Area, Controller, and Action. To use Browser EUM with .NET Core on the full framework, you need to use Assisted Injection for the Javascript Agent.

  • The .NET Agent includes correlation support for Service Remoting in Azure Service Fabric.
  • The .NET Agent supports the Task return type for Method Invocation Data Collectors.

  • The .NET Agent includes the following backend and remote service updates:
    • Improved naming for Azure Table and Azure Blob backends.
    • Support for the MongoDB version 2.2 sync API.
    • Support for the Redis StackExchange client.
  • .NET Agent requires Universal C Runtime. If the installer warns you that it is not installed on your Windows server, take one of these steps:

Node.js Agent Enhancements

  • You can configure your logging settings to log to STDOUT by setting the outputType parameter in logging settings. For more information, see Node.js Agent Logging.
  • In Process Snapshots, you can view data on asynchronous activities in the Node.js event loop for N|Solid processes. For more information, see N|Solid Monitoring Data.
  • For the txn.addSnapshotData and txn.addAnalyticsData methods, the key and value arguments are no longer coerced to string. Numeric values are properly passed as integers, floats, etc.

Upgrade Notes

  • BrokerURL is no longer supported as a backend identification name for Kafka consumer backends. If using it as a naming property, you will need to change the configuration to use another identifying property. 

Resolved Issues

APMPLAT‑138Last JVM start time showing current date on node list dashboard
APMPLAT-524Application List Flow View doesn't show EUM application
APMPLAT-540Frequent logging with "Invalid principal name: ANONYMOUS" for hotspot learning 
APMPLAT-727Clicking the All Other Traffic BT in Tier Snapshots navigates to different All Other Traffic BT
APMPLAT‑923Metric browser log scale rendering is broken when values contain non zero, zero, and no data
APMPLAT-978Business transaction configuration UI for .NET incorrectly indicates Perl-style regular expression support
APMPLAT-1366Rest API calls failing due to encoding issue 
APMPLAT-1552Business Transaction list slow response when searching/filtering
APMPLAT-1569500 ISE exception appears when a read-only user tries to exclude a service endpoint on the SEP Dashboard 
APMPLAT-1573Same value for current and average value in dashboard
APMPLAT‑1602Duplicate "All Other Traffic" per tier on business transaction limit reached 
APMPLAT-1754Machine agent keeps consuming license even though the machine instance has been deleted
APMPLAT-1854Creating rule in Live Preview for POCO BT, the Name text box loses focus
APMPLAT-1855Exceptions list illegible due to overlaid text
APMPLAT-2061Machine Snapshot with Archive enabled do not show as Archived in Controller GUI
APMPLAT‑2064RBAC: Configure Service Endpoint not working at application/tier level
APMPLAT-2117Improved performance needed for hasEUMADDs 
APMPLAT-2236'Deleting' message needed when events are being deleted
APMPLAT-2245Application dashboard performance issues due to getMobileApplicationsCount
APMPLAT‑2355Unable to download JVM Crash Logs with 403 forbidden error
APMPLAT-2415Application import did not import enabled POJO Business Transaction Match Rule
DOTNET-570Coordinator service hangs during restart
JAVA-543Ignore logged messages does not work with ignore exception
JAVA-696Merge delimiter is not used for ADO.NET/WebService/WCF/MongoDB Backend detection
JAVA-761NPE for instrumenting webObject
JAVA-896HTTP backends not being identified with BsonSerializationException
JAVA-909End-to-end latency is not reported for Tibco BW Process
JAVA-928Incorrect exit call count reported for exits based on Sun HttpURLConnection class in some cases
JAVA-1196Exception chain not differentiable from list in snapshot view in UI due to repeating same exception name
JAVA-1210Instrumentation broken for TibcoHttpEntryPointInterceptor
JAVA-1278Neutralization Error for com.singularity.snapshot.CallStackSampler
JAVA-1333Custom DB classes instrumented, but do now show up in snapshots or flow maps

Known Issues

  • If you enable Kafka consumer entry points for the Java Agent, the flow map shows the data flow in reverse from the node to the Kafka cluster.
  • Inactive nodes do not get marked as historical despite appdynamics.jvm.shutdown.mark.node.as.historical being set to true.

Database Visibility Notes



  • In the Execution Plan Window, the cached plans for SQL Server are rendered as diagrams for better readability.

Resolved Issues


DBMON-39Unable to see transaction snapshot for Microsoft SQL Database
DBMON-240Run-Duration sorting should be numeric
DBMON-388Collecter UI shows "agent is currently not reporting data"
DBMON-1028Missing executions and avg response time for SQL Server 2005 sp4
DBMON‑1228Database URL is broken after selecting custom time range

End-User Monitoring Updates



Browser RUM

  • To perform automatic injection for .NET, you no longer need to set the attribute runat="server" in the <head> element of the master or the aspx page.

Mobile RUM 

  • The Xamarin Agent, in addition to reporting native app crashes, now also reports uncaught exceptions. You can view the stacktraceintheCrash Details dialog, which will include the class and methods called. If you are in debug mode, you can also view the file names and line numbers in the stack trace.
  • The usage stats for connection types given in the Usage Stats tab of the Mobile Dashboard are now based on network requests, not app opens.
  • In addition to reporting crashes, network requests, usage stats, and sessions, Mobile RUM now also reports a number of non-fatal issues that don't cause crashes but negatively impact the user experience. The primary app issue is known as "application not responding" or ANR, but the list of non-fatal issues extends to security issues, UI issues, and exceptions. For this version, Mobile RUM will only support the non-fatal issues such as ANRs and exceptions.

Browser Synthetic Monitoring

  • You can install and run Synthetic Private Agents on internal networks to monitor internal websites or services that aren't visible to the public Internet. You can also use Synthetic Private Agents to test from specific locations or within your premises. Synthetic Private Agents require a separate license allocation from Hosted Synthetic Agents. 
  • Synthetic jobs can now check the availability of resources. You can set the session state to "Warning" or "Failed" when a resource is missing, and configure alerts accordingly. See Configure Availability Rules to learn how.
  • You can choose a mobile browser to run a script or URL measurement. The synthetic job runs Chrome in the mobile emulation mode with the profile properties for the selected mobile browser.

Resolved Issues

Browser RUM 



The EUM Installer fails on Windows when the Database password has the character '^'
BRUM-8The EUM Installer fails to connect to the Events Service over HTTPS configured with custom CA certificates
BRUM-9Uninstalling the EUM Server on Unix machines can in some cases remove the Controller installation
BRUM-10EUM Upgrade: Silent EUM upgrade doesn't take into account the mysql.dbHostName parameter in a split-host setup
BRUM-272Some IP addresses resolve to a country named "Asia/Pacific Region"
BRUM-308The EUM Installer does not preserve a customer's root certificate
BRUM-829Validating large mapping files causes an "Out of Memory Error" (OOME) on the Geo Server
BRUM-942When configuring applications, the App Server Agents incorrectly fetch non-business applications, such as EUM apps
BRUM-1089The EUM license does not get pushed to the EUM Processor until you create an application
BRUM-1141Upgrading to the JS Agent resulted in an increase of AJAX CORS errors
BRUM-1184The Getting Started page cannot send and verify a test page because of a "403 Forbidden" error
BRUM-1269Events service URL converted to http from https

Mobile RUM

MRUM-650The Controller's registration heartbeat that keeps apps and accounts alive is unreliable
MRUM-1036The cURL query to get the last 50 Proguard mapping file gives the first 50

Browser Synthetic Monitoring

SYNTH-59The synthetic session details dialog should always display a visual complete time for each page
SYNTH-1158Some types of failures have ambiguous error messages
SYNTH-1159Sessions stall when synthetic scripts open a second window and then close it.


EUMUI-108The server time in browser snapshots is greater than the overall end user response time
EUMUI-529The "Synthetic Requests per Minute" needs to be removed from the "Browser App List"
EUMUI-680The "Getting Started" wizard for creating EUM apps fails to check for existing APM application names
EUMUI-725Unable to export records on EUM_WEB_ANALYZE page
EUMUI-965The "Browser Sessions > Charts" tab uses the wrong unit of measurement for the "Least Available Jobs" widget
EUMUI-993The frequency dropdown misleads customers into thinking that jobs can be scheduled at 1-4 minute intervals

Infrastructure Visibility Notes

Integrated Network Visibility

With Integrated Network Visibility, you can 

  • Answer the key question quickly and easily: Is the network to blame for any performance issues in my application? 
  • Identify the root cause of performance issues in the application, the network, or in application/network interactions (i.e., how an application or server utilizes the network).
  • Pinpoint the traffic flows, individual nodes, and transport connections where network or application/network issues are occurring.
  • Collect detailed metrics that show how the network is performing and how well your application uses network connections and resources.
  • Collect and report targeted troubleshooting information to network, IT, DevOps, and other teams. 

Network Visibility is supported on Linux hosts with Java App Server agents. See Integrated Network Visibility.


Server Visibility Enhancements

  • Starting in November 2017, APM Advanced and APM Peak Edition licenses include one Server Visibility unit that covers one OS instance. Standalone licenses for Server Visibility are also available; AppDynamics sells each standalone license for Server Visibility in packs of 3, covering 3 OS instances. See License Entitlements and Restrictions
  • Server tagging makes it easy to query, filter, and compare related servers using custom metadata. You can tag related servers based on OS, location, tier, owner, or any other relevant criteria. Server tags provide additional context to server metrics.
    Server tagging is currently available for Linux, Windows, and Solaris. See Server Tagging.
  • The ServerMonitoringConfig.yml file (under <machine-agent-home>/extensions/ServerMonitoring) has the following changes:
    • The following settings enable you to configure the rate at which the Standalone Machine Agent collects specific sets of metrics on Linux hosts:
      • memoryMonitorConfig – memory metrics
      • cpusMonitorConfig – CPU metrics
      • volumeMonitoring > samplingInterval – volume metrics
    • The volumeMonitorConfig > blacklistSelectorRegex setting has been updated to exclude Docker volumes by default. This change was introduced to prevent high data loads that can occur from monitoring a lot of ephemeral Docker volumes. 

Resolved Issues

Server Visibility Resolved Issues

SERVER-1198Service Availability generates alerts even if DNS lookup is down
SERVER-1202Service Availability trims response data even after maxDownloadSize is increased in Controller
SERVER-1208Standalone Machine Agent throws exception when Docker Visibility is enabled: "chroot: can't change root directory to '/hostroot': No such file or directory"
SERVER-1211Fix to support turning off process monitoring when too many processes slow down performance on Standalone Machine Agent
SERVER‑1928Service Availability - Custom Filters not Working correctly

Standalone Machine Agent Resolved Issues

SERVER-8064.2.1 machine agent stopped reporting metrics when NFS volume became stale
SERVER-1210JVM Crash Guard does not report crashes after App Server Agent is killed (Machine Agent does not detect kill event)
SERVER-1213Memory Utilization metrics are not reported correctly on Windows
SERVER‑1370appdynamics-machine-agent.pid not present in /var/run/appdynamics
SERVER-1551Standalone Machine Agent does not handle backslash character correctly on Solaris 11
SERVER-1639Metric Browser > Server & Infrastructure does not show Custom Metrics folder 
SERVER-1640Machine agent fails to collect raw data
SERVER-1696<use-simple-hostname>true</use-simple-hostname> not working as intended
SERVER-1710Linux Machine Agent cannot handle /proc/partition files that have a lot of partition entries
SERVER-2120Standalone Machine Agent cannot collect OS metrics on Red Hat Enterprise Linux 7.4


Known Issues

Server Visibility Known Issues

  • If a metric name contains colons or pipe characters (: or |), the Metric Browser interprets the name as hierarchically separated. These characters could appear in a process name, a disk or partition name, a mount point, or a network interface name.
  • A machine agent enabled for the 4.1 Server Monitoring Beta will not work with a 4.4 Controller. To continue using Server Visibility (previously Server Monitoring), upgrade both the machine agent and the Controller.
  • If the machine that a Machine Agent is monitoring goes to sleep, monitored processes might be duplicated on the Controller. Because the process has a new start time, the Controller interprets it a new process. When the configured process count is reached, the Controller marks the duplicated processes as terminated and purges them.
  • (Windows only) You must have .NET Compatibilty Mode enabled for Server Visibility to work correctly on a server with a .NET APM agent installed.
  • Server Visibility does not support the following on Solaris:
    • Solaris zones
    • Unicode characters
  • The following Health Rule is disabled by default in this release: 
         Disk Usage is too high on at least one partition. 
    This wildcard health rule can result in high resource consumption and health rule evaluation times on the Controller. If this rule is critical for your environment, the recommended practice is to create your own custom Health Rules and apply specific rules for specific volumes on specific servers. For more information, see the following Support Advisory:

Docker Visibility Known Issues

  • The Standalone Machine Agent running inside the container sometimes reports a few extra volumes for the host machine. This can result in a higher total volume for the aggregate volume metrics.
  • There might be gaps in the container network I/O metrics. This happens because the Docker API resets the accumulated network I/O metric data for every 4.2 GB of data sent or received. When the data is reset, the Standalone Machine Agent calculates negative I/O values and does not report a data point for that time window.
  • If the agent started monitoring the current container after the beginning of the selected time range in the Controller, the Controller might show metric data prior to the container start time. This metric data will include metrics from a previously monitored container. This behavior occurs when the Controller flag "sim.machines.reuse.enabled" is enabled. 
  • If the agent started monitoring the current container before the beginning of the selected time range in the Controller, the data is correct for the current container.
  • If a container stops running while it is being monitored, the Tiers & Nodes Dashboard > Server tab will show data for the stopped container rather than for the underlying server.
  • In some cases, container monitoring is suspended when some containers that are currently being monitored are stopped. This issue has been observed on Docker API version 1.24. The suggested workarounds in this case are to
    • Restart the Standalone Machine Agent (Docker Visibility will start monitoring the containers), or 
    • Upgrade to Docker CC/EE v17.03 or Docker Engine v1.13.

Standalone Machine Agent Known Issues

  • Reset Machine Agent action on the AppDynamics Agents window is not available for 4.4 Machine Agents.
  • (Windows only) The JavaHardwareMonitor extension and the ServerMonitoring extension (introduced in 4.2) assign network names differently. If you have any health rules based on JavaHardwareMonitor names, and you want to use these rules with the ServerMonitoring extension, you will need to update the names that these rules are based on.

Application Analytics Notes

Enhancements and Updates

Agent Status

Visualization and Widgets

  • Funnel widget improvements include:
    • The ability to display the performance overlay on the funnel bar and show how many of the participating events in the step are in normal or slow or in error category. This is the Show Health option in the properties pane.

    • Ability to see the underlying events related to abandoners (drop-offs) at each stage of the funnel.

    • Visual layout improvements

  • Property panes have been added to the Analytics widgets to provide more control over the widget appearance.
  • The transaction Live Stream widget is no longer supported.

Log Analytics

Business Outcomes

Business Outcomes are a way to monitor and correlate the data flow across multiple event sources. See Business Outcomes.

Experience Level Management

Experience Level Management (XLM) enables you to configure and schedule regular reports measuring performance against established service or experience levels. See Experience Level Management.

Upgrade Notes

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:

  1. Preserve the old watermark file so that you can copy it to the corresponding location in the new <analytics-agent-home> directory structure.
  2. Preserve your pre-existing job files so that you can copy them to the corresponding location in the new <analytics-agent-home> directory structure.

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 4.3 or 4.4 agents, 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 analytics-dynamic-service-enabled node property. 

If you change the analytics-dynamic-service-enabled node property through the Agent Configuration UI (updating the analytics-dynamic-service-enabled node property directly) it will have no affect on version 4.3 or higher Java Agents.
Related Background

Version 4.2 and earlier app server agents use the analytics-dynamic-service-enabled node property to enable Transaction Analytics. Using the node property directly allowed for disabling and enabling the Analytics Dynamic Service at the application, tier, and node levels. The Analytics Configuration UI allows for setting this property only at the Application level. Therefore, Java Agents 4.3 and higher are not be able to disable or enable the Analytics Dynamic Service at the tier and node levels.

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 analytics-dynamic-service-enabled property. Therefore, if you use one of these import mechanisms to enable or disable the Analytics Dynamic Service and you have a mixture of old (pre 4.3) and new (4.3 and higher) agents, you must manually set the associated analytics-dynamic-service-enabled property to match the Analytics Dynamic Service configuration value. The analytics-dynamic-service-enabled node property can also be set as part of the Application Import and has its own Import REST API (accessed at POST /setAgentProperty). See: Import Application Analytics Dynamic Service Configuration at Configuration Import and Export API.

Resolved Issues


ANALYTICS-1339Analytics table widget should retain column width in Custom Dash
ANALYTICS-1375Scrolling analytics searches in Chrome results in jumping straight to the bottom of the page
ANALYTICS-1395No validation when zooming in on analytics query
ANALYTICS-1424Analytics UI : hide/unhide does not work for custom fields having special characters
ANALYTICS-1442Page Name column wrapped up on dashboard and report on Analytics -> Custom Widget Builder
ANALYTICS-1754Browser Analytics: Timestamp field needs to be fixed
ANALYTICS-1981Data collectors populating incorrect values in analytics
ANALYTICS-2301Type ahead auto completion only works for the first 100 entries

Proxy settings in admin.jsp requires controller restart


Funnel widget steps do not allow drop-down selection of more than 100 records

ANALYTICS-3379Unrecognised field "error_details" for Analytics widget in custom dashboard
ANALYTICS-3262ADQL returning only the first element from the data collector list

Known Issues

  • To deploy the Analytics Agent on Linux using the Universal Agent, you must use machine-agent mode.
  • Windows: You can not delete a log file with the "del" command while the analytics agent is collecting log data from the file.
  • For Analytics Searches: 
    • In Basic mode, regular expressions and the NOT logical operator are not supported for free text search. 
    • In Basic mode, quotes and commas have no special meaning.
    • Saved Searches from 4.1 can be imported multiple times if you click 'Import from 4.1' button multiple times.
  • Due to timing issues, full information for business transactions may not appear immediately when running a Transaction Analytics search.
  • If you have deployed EUM such that you are using an on-premises Events Service for transaction and log analytics data, and the SaaS Events Service for your EUM data, you can not query the browser or mobile request data using the Analytics API.
  • When defining Business Outcomes, you can not delete the same field from one milestone and add it to a different milestone in the same Save action. To workaround this issue, delete the field from the first milestone and save the definition. Then edit the Business Outcome again and add the field to the second milestone and save the definition.

AppDynamics On-Premises Platform Notes

The following notes describe updates to the AppDynamics on-premises platform, including the Controller, Events Service, and EUM Server components. 


Enterprise Console

  • The Enterprise Console (formally known as the Platform Administration Application) is the installer for the Controller and Events Service. You can use it to install and manage the entire lifecycle of new or existing AppDynamics Platforms and components. The application provides a GUI and command line interface that you can use to perform the following tasks:

     Multi-Platform Management

    • Manage multiple platforms at the same time using the application
    • Discover, install, and upgrade Controllers, Event Services, and MySQL nodes

    HA-LifeCycle Management

    • Manage High Availability (HA pair) lifecycle without the use of the CLI based HA-toolkit or sudo privileges
    • Perform failover management

    Other Features

    • Manage Controller and Events Service lifecycle
    • Utilize GUI & CLI support
    • Manage AppServer and database configurations

    See Enterprise Console for more details.


  • The default values for Event and request segment data (RSD) rate limits have been set to 7,000 and 30,000, respectively. This will reduce the need to update the values as the new default values are based upon realistic expectations.
  • The default value for the flag, application.diagnostic.data.purge.enabled, has been set to true. You can update the flag value in the Controller Settings. This setting helps with clearing up disk storage space by purging stale entites and their metrics.

EUM Server

  • The EUM Server product installation now allows you to install the EUM Server and a MySQL database instance on a single host.
  • If you have migrated your EUM Server from version 4.3.x or earlier to version 4.4,  you must migrate the MySQL instance previously stored on the Controller host to the EUM server host. For instructions, contact your AppDynamics Sales or Professional Services team.

Events Service

  • The IllegalStateException error generated when the Controller is not connected to an Events Service is now throttled to once per minute. There is also a change in logging messages, where EJBException is now a ControllerTimerTaskBean exception, when the Events Service is not configured.

Upgrade Notes

  • You can upgrade your Platform with the Enterprise Console. The Enterprise Console simplifies the upgrade process by allowing you to discover and upgrade Controllers, Controller HA pairs, and Events Service thought its GUI. You can pick and choose the platform or service to upgrade once your Enterprise Console is installed or upgraded. The Enterprise Console supports Controller (standalone and HA-pair) and Events Service upgrades starting from 4.1 and higher to the latest version. If you are on an earlier version like 3.x or 4.0.x, and would like to upgrade to 4.4, you would need to use the package installers and first upgrade to 4.1. Then use the Enterprise Console to upgrade to 4.4. See Upgrade Platform Components for more details.

Resolved Issues


ECONSOLE-270Mac OSX Platform Admin installer is corrupt due to Oracle JRE changes
ECONSOLE-711References to the 4.2 Platform Admin remain after upgrading to 4.3
ECONSOLE-938Controller 4.3.3 Installer fails with varfile usage
ECONSOLE-968Installer does not check for overlap between MySQL data directory and other installation directories
ECONSOLE-1052"Port number xxx conflicts" for the TCP/Unicast port error
METADATA-624Unable to create user with username "root" in 4.3
METADATA-1284Unable to delete custom role due to Controller permission migration
METADATA‑1432Obsolete child metric to virtual metric relationships are not invalidated and removed from the metadata cache when updating virtual metrics
METRICSVC-374Multiple time-slices for rollup breaks custom dashboard widgets
UIPLAT-2334.3 Controller login page loads very slowly on IE

Known Issues

  • A known issue prevents the Controller database from starting at installation time if another instance of MySQL is running on the machine. Certain Linux operating system distributions include MySQL. If the bundled MySQL instance is running, you will need to shut it down to complete the AppDynamics Controller installation.
  • To run multiple Events Services on a Windows box, copy the bits to multiple directories and install them as service. A unique suffix to the Events Service service name will be auto generated based on the directory path of the bits. The executor on Windows does not support changing the process name in properties files.

Deprecation and End of Life (EOL) Notices

  • The AppDynamics Java Agent will no longer support monitoring Java applications running in the Java Development Kit 5. See Desupport Notice: Java Development Kit 5.
  • Mobile RUM: Dynamic Info Points are no longer available for Android apps.

  • End-User Monitoring: The option View Dark Mode has been removed from the Geo Dashboard.

  • Server Visibility (formerly Server Monitoring): The "Disk Usage is too high on at least one partition" health rule is now disabled. See Support Advisory: "Disk Usage is Too High" Health Rule is Disabled in Release 4.3 and Higher.
  • The Controller UI is no longer supported on IE 9. IE users are advised to use IE 10+ versions when using the Controller UI.
  • The Controller Package Installer is no longer supported. The Enterprise Console application supports most of your platform deployment needs, including installing a Controller and Events Service. Updates

Resolved Issues

ANALYTICS-4104Custom User Data Missing From ADQL Data Grid
METADATA-1905Flow map loads very slowly after upgrade Updates 

Resolved Issues

APMPLAT-3167Wrong name and exit type for DynamoDb remote services after upgrade Updates 

Affected Artifacts

  • Enterprise Console

Resolved Issues


ANALYTICS-3772Scheduled queries observed in SaaS instances run every 15 mins with excessive duration and no metrics
ANALYTICS-4516Metric jobs fail with java.util.concurrent.CancellationException
BRUM-1957Controller threads leaking, resulting in out of memory errors
DBMON-1483Deploying a large number of DB Agents causes agent pool saturation 
ECONSOLE-1932Backup Controller upgrade fails due to keystore file mismatch between primary and secondary Controllers 
  • No labels