Anomaly Detection

For anomalies related to base page experience and network request, you can now view the issue summary and actionable recommendations generated by AI. AppDynamics SaaS uses AI to correlate all the metrics associated with an anomaly and generates comprehensive summaries of the issue and the top three suspected causes, which helps you to understand the issue better. It ranks the top three suspected causes and provides recommendations on how to resolve the issue. This saves your time because you do not need to manually correlate various metrics by referring to multiple dashboards within the Controller to understand the issue. This enhanced anomaly detection provides a better user experience and information access to reduce the mean time needed to detect the root cause and resolve the issue.

26.1.0

February, 2026

Alert and Respond

For a health rule violation, you can now view the AI-generated summaries of the issue and its suspected root cause in a revamped user interface. You can view the top three suspected root causes and the AI-generated summaries of the causes related to the health rule violation. This helps to reduce the mean time to identify performance issues in your applications and infrastructure.

26.1.0

February, 2026

Alert and Respond

When you create a health rule, you can now select the Exact match one wildcard * to one level of directory option to enforce a strict matching pattern in the relative metric path. For example, if you specify the following relative metric:

Custom Metrics| WebsphereMQ-2|*|Status

The * wildcard replaces only one string between the two pipes in the actual metric path. The health rule evaluates only on the following actual metric path:

Custom Metrics| WebsphereMQ-2|UXSOAGWSG51.QM1|Status

and excludes the paths such as

• Custom Metrics| WebsphereMQ-2|UXSOAGWSG51.QM1|Channels|SOASG.TLMRP|Status

• Custom Metrics| WebsphereMQ-2|UXSOAGWSG51.QM2|Channels|SOASG.TLMRP2|OIRDFF.SEEP|Status

By default, you can use a maximum of four wildcards * in the relative metric path. For example, the metric path Hardware *| *|*|* represents the actual path such as Hardware Resources|Network|en0|Outgoing KB.

26.1.0

February, 2026

Alert and Respond

In Create Health Rule wizard, you can now view and select the network requests for a specific mobile app. This enhancement enables you to monitor the network requests from a particular mobile app. You can configure a health rule to generate alerts whenever these network requests exceed or fall below the specified critical or warning thresholds, helping you proactively identify and address performance issues.

26.1.0

February, 2026

Controller

This release of Controller introduces the Historical Node filter on the Tiers & Nodes and Metric Browser pages, allowing you to easily view and analyze nodes that are marked as historical. This enhancement improves visibility into inactive nodes that are retained for historical performance data analysis.

26.1.0

February, 2026

Controller

Controller displays the Language selector by default under User Profile > My Preferences > View Preferences. You can change between English and Japanese. To hide the the Language selector, set the locale.switch.controller.enabled property to false.

26.1.0

February, 2026

Controller

26.1.0

February, 2026

• Show Baseline
• Apply Baseline Color
• Reverse Color Order

• variables for the following widgets:
  • Label
  • Image
  • Iframe
• variables for the widget title and subtitle

Licensing

The License page for both Agent-based Licensing and Infrastructure-based Licensing accounts is redesigned to deliver an improved user experience. You can view the following enhancements:

On the License Rules page, you can now view:

• the license usage details across all your applications with a single click on any license rule. This enhancement minimizes the number of clicks required to access detailed license usage information.
• the access keys associated with your license rules.

The License Rules page now loads significantly faster, even if your account contains a large number of defined license rules. This improvement ensures quicker access and a smoother experience when managing license rules.

On the License Summary page, you can now view:

• the exact license usage count such as 1000 instead of 1K.
• the license expiry dates for all your license entitlements.

On the Reporting page for the Agent-based Licensing account:

• The Select Applications wizard now loads the applications more quickly when you begin typing an application name, allowing you to find and select applications with improved speed and efficiency.
• You can sort the columns in the USAGE BREAKDOWN table. This action enables you to view applications according to license usage for easier analysis and comparison.

26.1.0

February, 2026

Licensing

For the Agent-based Licensing account, you can now view the license usage metric of each application in the License > Application level usage tree in the Metric Browser. This feature allows you to track the license consumption trends of all applications running in your environment over time. By analyzing these trends, you can make informed decisions to allocate licenses efficiently based on actual usage requirements. The Usage (LU) metric for each application can be used to create health rules. These health rules enable you to receive alerts whenever there is a deviation from the normal license usage pattern, helping you proactively manage license consumption and avoid potential issues.

For both Agent-based Licensing accounts and Infrastructure-based Licensing accounts, you can now view the Utilization (%) metric for each component in the Account dropdown within Metric Tree of the Metric Browser. This metric represents the percentage of Usage licensed units. You can use the Utilization (%) metric to create health rules and set warning thresholds such as 80% or 90%, regardless of your current licensing configuration. This provides a convenient way to monitor usage and manage health rules.

26.1.0

February, 2026

Unified Observability Experience

You can now integrate Splunk AppDynamics SaaS with either Splunk Cloud Platform or Splunk Enterprise, even when these services are deployed in different cloud regions. This enhancement allows you to select a Splunk tenant located in a separate region from your AppDynamics Controller tenant, enabling seamless access and visibility of your application logs directly within the Splunk dashboard. This flexibility helps your organization to manage and monitor distributed applications more efficiently across multiple regions.

26.1.0

February, 2026