Release Notes

This release includes bug fixes, see,  Cisco AppDynamics On-Premises Resolved Issues.

This release includes bug fixes, see,  Cisco AppDynamics On-Premises Resolved Issues.

This release includes bug fixes, see, Cisco AppDynamics On-Premises Resolved Issues.

From the License Summary Dashboard, you can view the point-in-time data for your Infrastructure-based Licensing (IBL) Secure App license usage.

• You can now create health rules for business transactions with tags criteria. You can use API or Controller UI to create the rule. Specify tag keys and values for the business transaction that you want to monitor. The health rule monitors all the business transactions with the matching tags. See Health Rule API and Health Rule Entities.

• In an HTTP action template, you can now use the OAuth 2.0 authorization to send alerts to a third-party application. This helps to secure the alerts that are sent from the Cisco AppDynamics On-Premises Controller. HTTP action template supports two types of OAuth 2.0 authorization:

  • Authorization code OAuth
  • Client credential OAuth
    See HTTP Request Actions and Templates.

• In HTTP Request Template, you now have the option to retry an HTTP action after it fails. The retry mechanism works when an HTTP action fails because of the following reasons:

  • CONNECT_TIMEOUT_EXCEPTION

  • CONNECTION_POOL_TIMEOUT_EXCEPTION
  • NO_HTTP_RESPONSE_EXCEPTION
  • JAVA_NET_SOCKET_EXCEPTION
  • JAVA_NET_CONNECT_EXCEPTION
  • Status code specified in the Failure Criteria option of the template

  When you select the Retry on Failures option, an attempt is made to send the HTTP action to the configured third party application. The maximum number of retry attempt is two. See HTTP Request Actions and Templates.

• You can now use the following APIs to enable and disable all the health rules of an application:
  • POST <controller_url>/controller/alerting/rest/v1/applications/<application_id>/health-rules/enable
  • POST <controller_url>/controller/alerting/rest/v1/applications/<application_id>/health-rules/disable
See Health Rule API


The new look and feel of the Controller UI is designed to enhance the user experience. See General Navigation.

Here are the major changes:

• Updated Navigation Path: The navigation path within the Controller UI is revamped for a more intuitive experience. The main menu is now accessible from the left pane, replacing the previous top menu bar.
• Applications Menu: The Applications menu is now displayed on the left pane, listing all available applications. You can then choose an application to navigate to the details.
• Consolidated User Settings: All user details are now conveniently located in one place within the user settings option. You no longer need to enable the miniprofile.controller.enabled property in the admin.jsp page to view your personal profile.
• Help Menu: The help and support information is now available within the help menu under the help icon.

The following libraries are upgraded:

Support for monitoring the SAP HANA database. You require Database Agent >= 24.5.0 and Controller >= 24.7.0. See:

• Database Visibility Supported Environments
• Configure SAP HANA Collectors

• SAP HANA Metrics

The BLOCKING_SESSION event is now supported for the Oracle database. You require Database Agent >= 24.7.0 and Controller >= 24.7.0. 

See Database Events Reference.

License Usage Reporting

For Agent-based Licensing (ABL), you can now generate license usage reports for one or more applications from License > Reporting. The report breaks down the licensing units for agents. It also indicates how many license units originate from APM microservices that can be filtered through Controller properties and Cluster Agent data. Finally, you can export and download the report as a CSV file.

ANLYTCS_ES-16217

Flow maps of Business Transactions do not load after migrating the data to Elasticsearch 8.x.

CONTRLRDEV-4120

The business transactions promoted from the Overflow tab are not displayed in the first-class business transactions list.

IAM-7264

The Controller SAML login does not work because the Account name field is not displayed for SAML login on the Single Tenant Controller.

The Controller login screen displays the account name even if it has a single tenant.

The Events API gives a 500 Internal Server error.

Widgets do not display any data for nodes. Also, the number of available nodes displayed is incorrect.

The Alert & Respond > Health Rules tab does not display any data.

-

The token generated while creating an HTTP request action using OAuth 2.0 and API clients fails.

24.6.0

CONTRLRDEV-4058

The Dashboards & Reports > Dashboards page does not display all the dashboards.

24.6.0 and 24.7.0

IAM-7243

The Controller login screen displays the account name even if it has a single tenant.

24.7.0

Cannot download the Analytics record in CSV format with ADQL query.

Cluster Agent does not capture the logs for restarted or Failed Pods on a Windows Controller.

• 23.9.0
• 23.11.0

The java.lang.string.intern() function causes latency in the Atomikos library.

The 500 Internal Server Error is displayed when you export an application from the Applications page in the Windows Controller.

The Metric registration limit reached error gets displayed even when the limit has not been exceeded.

The shared dashboard displays a blank screen

DBMON-9414

Database Agent

Database Agent does not report metrics for Oracle database.

Database Agent

Database Agent stops updating the logs.

Database Agent

Database Agent fails to start if you start using the InstallService.vbs file when Java is not installed on the host machine.

DOTNET-7265