AppDynamics Application Intelligence Platform

3.8.x Documentation



Release Notes

Child pages
  • Configure Diagnostic Sessions For Asynchronous Activity

AppDynamics Inc.

Skip to end of metadata
Go to start of metadata

Automatic Diagnostic Sessions For Asynchronous Activity

Diagnostic sessions are triggered based on the performance metrics for a business transaction. The average response time of a business transaction does not include the execution time of its asynchronous activity. If you have asynchronous processing in your application, it might be possible for the originating transaction to execute within normal bounds even though the asynchronous activity takes longer than normal. To diagnose an issue like this, you can create a custom health rule based on the average response time (or other performance metric) of the asynchronous activity and use that health rule to set up a policy that triggers a diagnostic session on the transaction. The general steps to do this are described in the following example that uses a metric for an async thread task.

  1. Create a custom health rule based on the asynchronous metric, such as average response time. The metrics for thread tasks are visible in the metric browser under the Thread Tasks node for transactions with asynchronous activity. Each thread task has an individual node (usually its simple class name). Remember to select Custom as the type for the health rule.

  2. Create a policy that is based on the baseline of the asynchronous metric of interest, for example, the average response time.
  3. Configure the policy to trigger a diagnostic session on the affected business transaction.