Release Notes

Users can obtain one identity across Controller tenants and Accounts by completing an email address verification process. Once verified, users can use the same identity across multiple tenants and accounts, making it easier to manage their access and permissions.

See AppDynamics Global Identity Migration Experience - FAQ.

When you create or update a health rule for the type User Experience Browser Apps, you can now select the following metrics for the entities Pages or Virtual Pages:

• Visually Complete Time (ms)
• Visually Complete Time 50th percentile (ms)
• Visually Complete Time 90th percentile (ms)
• Visually Complete Time 95th percentile (ms)
• Visually Complete Time 99th percentile (ms)

These metrics are selected to evaluate the critical or warning criteria.

You can now configure a policy to detect a failed HTTP request action. An HTTP request action fails due to various reasons such as incorrect payload, server unreachable, or gateway timeout. In such scenarios, the policy triggers and you can set up an automatic notification through email or message. You can take corrective action accordingly.

You can now request your Cisco Accounts team to extend the health rule violation status beyond the default auto-cancelation period.  The health rule violation status gets canceled automatically when the health rule continues to violate straight for 72 hours.

ThousandEyes integration with AppDynamics support:

• Visualise network telemetry data from ThousandEyes
• Determine if network issues cause application issues
• Assess if network issues are impacting application performance
• Display network health rule violations from ThousandEyes

AppDynamics introduces Fleet Management that enables you to automate the agent operations such as installation, upgrade, and rollback.

When using Infrastructure-based Licenses (IBL), you have the option to enable license rules that help you conserve license consumption for a Cluster Agent when the system is unable to detect its vCPU information. In such cases, the Cluster Agent without vCPU information will be rejected and won't be registered. This helps you avoid consuming a license for the agent.