AppDynamics Application Intelligence Platform
This topic covers release information for AppDynamics Pro versions 3.8.x.
If you are reading this in PDF format, many links will open in the product documentation wiki. AppDynamics continuously improves its product documentation. The most current release notes are on the wiki at Release Notes for AppDynamics Pro.
|Controller||Remediation scripts fail to run with argument list too long error|
|Agent||Agent backend limit not respected at startup|
Java Agent performance problems related to JDBC backend naming rules
|Agent||Spring RMI instrumentation not applied|
|Agent||IndexOutOfBoundsException exception generated due to cross-tier correlation errors when business transaction limit is exceeded|
After a data collector configuration is deleted, errors appear in the dashboard showing any Business Transaction previously associated with the collector
|Controller||Open incidents not canceled when their associated violating health rule scheduled period ends|
|Controller||Slow dashboard loading in the UI due to incorrect cache misses|
|UI||"All Other Traffic" is labeled APPDYNAMICS_DEFAULT_TX in the End User Experience Management (EUEM) UI|
A problem that was causing the tier dashboard to load very slowly has been fixed.
The Linux version of the modifyJvmOptions utility now prevents you from adding a Java option that has the same name as an existing option in the domain.xml file. Previously, it permitted adding an option with the same name as an existing option as long as their values were different. In practice, this often resulted in unintended redundant entries in domain.xml. You must now remove the existing option before adding an option with the same name. Also, a new command for the Linux version of the utility has been added. It prints the existing options in domain.xml. To use it, enter:
For more information about modifyJvmOptions, see Modify GlassFish JVM Options.
404 calls no longer register a new business transaction when MVC Controller cannot be found
Improved support for applications using WeakReference
Resolved a memory leak related to AzureBlobExitInterceptor
Improved business transaction support for ASP.NET 4.0 pages that use the Page property of Async="true"
|.NET Agent, Controller|
Resolved an issue with ADO.NET DB exit calls auto-resolving to the tier
Resolved an issue with EOFException on Sun RMI JRMP result stream
Now delay AMX booting for GlassFish
|Agent||Fixed naming of business transactions for custom match rules of type Servlet that use URI segment naming such that resulting name is patterned after <Match Rule>.<URI segment 1>/.../<URI segment n>|
No longer correlate when cross-Controller requests are detected
Resolved a minor issue that caused an IllegalArgumentException: inconsistent range
Information point method names are no longer truncated at 100 characters; now support up to 500
For new installations, the app server administration account password is now the same as the Controller root user password
The agent now supports OCI8 and a connection method which uses the file "tnsnames.ora"
The RPM installer no longer sets the PHP agent log to /agent.log
Resolved a NullPointerException in proxy logs during agent startup
|Android Agent, iOS Agent, UI|
Resolved a UI problem displaying data for iOS and Android
Fetching all Browser Snapshots for extended periods, like a month, could take a very long time, particularly when the underlying data is sparse. The requests for this functionality have been optimized and response time is much improved.
|App Agent for .NET||Uninstalling the agent no longer results in a cmd prompt on Windows|
|App Agent for .NET||Resolved issue that could cause the .NET agent to not report properly|
|App Agent for Java||Improved correlation support using Remote Actors on Akka version 2.3.1|
|App Agent for Java||Resolved issue with monitoring a Sybase stored procedure|
|App Agent for Java||Resolved issue with extraneous error message when an already registered rule exception from JDBCRuleApplier is applied|
|App Agent for Java||Resolved a potential issue that could result in longer startup times for a server|
|App Agent for Java||Resolved a potential NPE in Agent Proxy|
|App Agent for Java||Resolved a issue that could result in a custom rule to stop working after upgrading to 3.8|
|App Agent for Node.js||Added distributed transaction correlation|
|Controller||Resolved issue with showing most expensive calls for stalled business transactions|
|Controller||Resolved a problem with health rule messages showing an incorrect JMX metric name|
|Controller||Resolved an issue with missing tier flow map data for current time range|
|Controller||Resolved a caching error that could cause metric gaps|
|Controller||Linux controller installer no longer fails if /tmp is mounted with the 'noexec' option|
|Controller||Resolved a potential issue that could result in a user's inability to login to AppDynamics through SAML Authentication|
|Controller||Resolved inconsistency with GC time spent and counts|
|Controller||Resolved upgrade timeout/rollback issue|
|UI||Reduced load time for Flash UI components|
|UI||Widget series now use different colors when adding new series|
|UI||Updated a confusing error message when exporting an application|
|UI||Resolved issue with page dashboard graphs not showing up when there is no data in the time range|
|UI||Improved the formatting of numeric metrics in Page Dashboards|
|UI||Browser snapshot grid and mobile network request snapshot grids now format dates consistently|
An on-premise Controller with End User Monitoring (EUM) enabled needs to be able to connect to the EUM Cloud aggregator. If the Controller needs to make external connections through an authenticating proxy, you can now specify credentials for the Controller to pass to the proxy.
You configure the credentials using two new Controller Java options:
The value of proxyPasswordFile should be the location and name of the file that contains the plain text password associated with the user identified by proxyUser. For more information, see Set Up and Configure Web EUM.
End User Response time is displayed in the Metric Browser in terms of percentiles (for this release, P90), regardless of the Controller used.
The App Agent for PHP now supports:
If a Web EUM instrumented page is associated with a server-side app agent, the cookie that the server-side app agent sets is now named ADRUM_BT instead of ADRUM_X_Y_Z as in previous versions.
New app agent node property capture-spring-bean-names can be used when a class is mapped to multiple spring bean names to display the class name instead of the spring bean name. See App Agent Node Properties Reference.
|App Agent for .NET||Fixed a problem with the agent parsing IIS6 hierarchies|
|App Agent for .NET||Fixed a problem detecting IBM WebSphere message queue exit points|
|App Agent for .NET||Fixed a problem with automatic injection of the EUM Footer|
|App Agent for .NET||Create a white list based agent|
|App Agent for Java||Added support for HTTP proxy authentication|
|App Agent for Java||Improved Akka support for Scala with closure methods|
|App Agent for Java||Fixed a problem with service endpoints on a JAX-RS based web service|
|App Agent for Java||Fixed a problem with some node properties not being set|
|App Agent for PHP||Fixed a problem with a segmentation fault in Apache 2|
|App Agent for PHP||Improved cookie handling|
|Controller||Fixed a problem with a repeating snapshot affecting metric registration|
|Controller||Added support for SAML group assertions|
|Controller||Fixed a problem where the upgrade process created a domain.xml with disabled http listeners|
|Controller||Fixed a database connection problem during upgrade|
|Controller||Improved top-level End User Experience dashboard load time|
|Controller||Fixed a problem with exporting applications|
|Controller||Improved URL information for SaaS alerts|
|Controller, UI, Mobile||Fixed a checkbox for enabling mobile APM|
|Controller||Improved TLS-1.2 Only (HTTPS) support|
|Controller||Fixed an installation problem on Win32 related to database shutdown|
|Controller||Fixed a problem affecting the MySQL Data Dictionary|
|UI||Fixed a problem with importing dashboards|
|UI||Renamed the "Network Connection Error" metric to "Network Error"|
|UI, Web EUM||Retained filter when navigating from page dashboard to browser snapshot|
|UI||Updated terminology for HTTP errors and network errors|
|UI, Web EUM||Page Dashboards no longer show negative numbers for related normal business transaction calls|
|Web EUM||Improved cookie handling|
The default security protocol used by the on-premise Controller has changed. For enhanced security, the Controller's secure listener now uses TLS 1.1 and TLS 1.2 instead of TLS v1.0 and SSLv3.
If using the Controller with an older version of the App Agent for Java or .NET framework, you need to be aware of security compatibility implications of the change.
This issue affects you if you have upgraded the Controller to 3.8.1 or later and still have any of the following deployed in your environment:
If you are affected by this issue, AppDynamics recommends that you upgrade the environment, as follows:
If upgrading agents or framework is not possible, you can re-enable TLS v1.0 and SSLv3 on the Controller. For instructions on reenabling the security protocols, see Configure the Security Protocol.
The following components have new and enhanced features in release 3.8:
The online documentation for 3.8 is now publicly available and does not require a login. It can now be indexed by the major search engines. To make comments on the topics, please login with your standard AppDynamics account.
Note: Not all UI changes are currently reflected in the documentation.
Policies and Alerts
Tighter Integration with AppDynamics for Databases Oracle Collectors
From a Transaction Snapshot Flow Map, where the exit call is to an Oracle database, you can link to AppDynamics for Databases 2.8 to see and analyze the exact SQL that was running at the time of the transaction snapshot. To enable this functionality, for the node containing the Oracle database, you must set the App Agent for Java node property jdbc-dbcam-integration-enabled=true. For more information, see Integrate and Use AppD4DB with AppDynamics Pro.
Previously, when the trial license expired for the AppDynamics Pro trial, it meant that you could no longer use the AppDynamics Pro instance. Now when the trial license expires, the AppDynamics Pro trial transitions to the free edition of the product, AppDynamics Lite.
For more information about the free edition of the product, see AppDynamics Lite.
The following section lists general security information for AppDynamics. For release-specific security information, see the update notes for that release.
The SSL Certificate Monitoring Extension is a new extension on the AppDynamics eXchange that reports the expiration date of SSL certificates on the machine as a metric to the Controller. The extension reports the certificate expiration date metric for the domains and at the interval you configure.
For more information, see the SSL Certificate - Monitoring Extension listing.
Obtain the Controller for your operating system from the AppDynamics Download Center.
Known issue: .NET 3.5 features are required in some cases to install the Controller as a Windows service. (.NET 4.0 installation alone may not be sufficient.) If you try to install the Controller as a service, the following error appears: "The following feature couldn't be installed: .NET Framework 3.5".
This occurs on the following versions of Windows Server:
The following instructions assume the use of Windows Server operating systems (which have the Windows Server Manager). If you encounter this issue on a non-server version, such as Windows 8, you need to download the .NET 3.5 executable and perform the equivalent installation.
To install .NET 3.5 features:
As a user in the Administrators group on the local computer, open Windows Server Manager.
Select "Add Roles and Features" and click Next.
Click Next until you get to the Server Selection screen.
Select the server on which you want to install the Controller as a service.
Click Next in the Server Roles.
In the Select features screen, expand .NET Framework 3.5 Features and select .NET Framework 3.5. Keep the .NET Framework 4.0 option selected.
You can now install the Controller as a service as described in the documentation.
For more information, see Upgrade the Controller.
When installing or upgrading the Controller on Windows systems that use a regional and language setting other than English (United States), the Controller installation or upgrade fails. The error message may indicate that the Controller database failed to start or that the setup processes failed to reach the Controller. The error occurs when the installer is attempting to start the Controller, and causes the installer to abort the installation or upgrade.
To work around this issue:
When the upgrade or installation is finished, edit the <Controller_installation_directory>\bin\controller.bat and replace the following line:
This line appears in the :startControllerDB section of the file. Notice the addition of quotes around both values used in the value comparison.
Save your changes.
Obtain the AppDynamics App Agent for Java download for your system from the AppDynamics Download Center:
For more information see:
Obtain the AppDynamics App Agent for .NET download for your system from the AppDynamics Download Center:
For more information see:
Fixed a problem with delays in backend discover configuration
|Controller||Fixed a problem with node based health rules being evaluated for a node not in the list|
|UI, App Agent for PHP||Fixed a problem with the RabbitMQ icon not displaying|
|EUMCloud, UI||Fixed a problem with alerts when page view limit was reached|
|App Agent for Java|
Fixed a problem with some node properties not being set
Improved performance of the EUM dashboard
Fixed a potential issue that prevented dashboards created with 3.7 from being import/exported