AppDynamics SaaS Controller Enhancements
Product / Component | Summary | Release Version | Release Date | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Business Transactions |
Note: This feature is supported on Java applications only and requires Java Agent 25.3.0 or higher. The release introduces the Override Lockdown option in the Rule Editor. This feature allows business transactions from specific rules to bypass the general lockdown, keeping them in the monitored list instead of moving to the overflow tab. It solves the problem of mixing transactions from critical and non-critical rules in the overflow bucket, especially aiding users with a large number of applications in capturing essential transactions as Business Transactions. The Override Lockdown feature is available only for Java applications. This feature:
From this release, the Overflow tab displays when the:
| 25.4.0 | May 30, 2025 | |||||||||||||||
Controller | This release introduces the UI based entity tagging using the new
See Tag Management. | page in the Controller UI. You can also access it from the left navigation pane. It is a user-friendly alternative to the Custom Tag APIs functionality. You can:25.4.0 | May 30, 2025 | |||||||||||||||
The following libraries are upgraded:
| ||||||||||||||||||
Anomaly Detection |
Splunk AppDynamics SaaS now automatically identifies anomalies in the following database metrics:
This anomaly detection removes the need for manually setting up health rules to identify database issues. It reduces both the mean time to detect (MTTD) and mean time to resolve (MTTR) incidents. See Anomaly Detection. | 25.4.0 | May 30, 2025 | |||||||||||||||
In the Anomaly Detection. page, you can now view the tier associated with a business transaction. You can correctly identify the business transaction if the same business transaction is associated with multiple tiers. In the email alerts, you can can view the tier associate with a business transaction. See | 25.4.0 | May 30, 2025 | ||||||||||||||||
Alert and Respond |
You can now create health rules on synthetic jobs to detect any user experience issues for browser applications and API monitoring. In the Create Health Rule wizard, select User Experience: Browser Apps or User Experience: API Monitoring and configure a critical or warning condition on the synthetic job metrics. You receive alerts when the metrics exceed the specified threshold value. See Create a Health Rule. | 25.4.0 | May 30, 2025 | |||||||||||||||
To create, update, delete, import, and override the alerting templates, you now require the If you are an account owner or administrator, the permission is enabled by default in your user profile. To enable the permission in other user profiles, contact your account owner or administrator. See Alerting Templates. | 25.4.0 | May 30, 2025 | ||||||||||||||||
Custom Dashboard |
You can now select the following time ranges on the dashboards and related reports:
| 25.4.0 | May 30, 2025 | |||||||||||||||
The | page now displays the last viewed date and time.25.4.0 | May 30, 2025 | ||||||||||||||||
Database Monitoring | This release supports:
| 25.4.0 | May 30, 2025 | |||||||||||||||
This release supports Always On monitoring for Microsoft SQL Server. You can monitor the availability groups in your Microsoft SQL Server clusters to troubleshoot incidents in your production environment. See Always On Cluster Window. | 25.4.0 | May 30, 2025 | ||||||||||||||||
You can now monitor and track storage utilization of your Microsoft SQL Server databases. Drill down from the Databases and Filegroups tabs to the individual data files on the Data Files tab to identify any unexpected storage spikes. See Database Files Window. | 25.4.0 | May 30, 2025 | ||||||||||||||||
While monitoring Amazon RDS, the Access Key and Secret Access Key fields are now optional. You do not need to specify these details if the Database Agent is deployed on an Amazon EC2 instance using the same Amazon Account as RDS and can access CloudWatch. See Complete the Hardware Monitoring Section. | 25.4.0 | May 30, 2025 | ||||||||||||||||
Licensing |
The following enhancements are designed to provide greater visibility and control on your license metrics:
Note: This documentation mentions a feature that is currently only available as an early preview ("Beta"). Splunk AppDynamics reserves the right to change the Beta and its documentation including the content herein, at any time, for any reason, and without notice or compensation to you before making it generally available as well as never making it generally available. This documentation is not a guarantee of future product features and should not be relied upon in making any purchasing decisions. Actual product results may vary from forward-looking statements due to factors including but not limited to: changes in Splunk AppDynamics and third-party technologies, factors related to the economy and target markets, acquisitions of other companies, the hiring and termination of personnel, and other factors. Please refer to the full terms at
https://www.splunk.com/en_us/legal/appdynamics-limited-license-agreement.html for details. | 25.4.0 | May 30, 2025 | |||||||||||||||
The Controller UI displays a grouped notification for the registered agents when there is no vCPU information. The notification is displayed every 15 minutes based on the agent host IDs. | 25.4.0 | May 30, 2025 | ||||||||||||||||
You can now create license rules for End User Monitoring (EUM) to allocate the total license units among the Browser Real User Monitoring (BRUM) and Mobile Real User Monitoring (MRUM) applications based on your usage patterns. This feature helps you to efficiently manage the Splunk AppDynamics SaaS licenses in your applications. See End User Monitoring License Rules. | 25.4.0 | May 30, 2025 | ||||||||||||||||
Metric Browser |
This release introduces the search functionality on the Metric Browser - Server Visibility page to search for any specific metric group within the first four levels of the metric tree. You require minimum three strings to initiate a search. When you specify the string in the search field and click Search, you can view the total number of matches found with the navigation arrows to move to previous or next match in the sequence. See View Metric Browser | 25.4.0 | May 30, 2025 | |||||||||||||||
Analytics | ADQL queries supports CASE clause. You can use the CASE clause within the SELECT clause to add conditions to your ADQL query. It helps you to transform data with the specified condition. This clause supports aggregation and bucketing functions. See CASE Clause. | 25.4.0 | May 30, 2025 |
Agent Management Enhancements
There are updates to Smart Agent. See Smart Agent Enhancements.