Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Health rules: define key performance metric thresholds for your application, across the stack.
  • Policies: link health rule violations, and other performance-based events, with appropriate actions.
  • Actions: automate what should be done in response to a wide variety of situationsevents, including such as sending alerts and performing diagnostic and remedial tasks.
  • Email digests: send a compilation of messages sent to a recipient list when specified events occur.

The system provides for the creation of email templates and HTTP request templates. These templates can be re-used to create actions for various applications in the account as well as facilitating integration of the alert and respond system with third-party email and HTTP APIs.

Sample Use Cases

The AppDynamics platform recognizes some broad-based health issues commonly experienced by applications, such as "Business Transaction response time is much higher than normal" or "Memory utilization is too high". These are configured as default health rules, which define how high is "much higher than normal" or "too high". Use policies to attach these rules to alerts (whom to notify) and responses (what to do) when these problems exist. You can use these rules "as is" or modify them for your environment. See Default Health Rules.


  • You have an application that performs well for normal load. However, peak loads can cause the application to slow. During peak load, AppDynamics not only detects the connection pool contention, but also allows you to create a remediation script that can automate increasing or decreasing the size of connection pool. You can require human approval to run this script or simply configure it to execute automatically when it is triggered. Create a runbook and associate it with a policy so that it will fire when the connection pool is exhausted.

Products that


Alert and Respond

Policies, health rules, actions, and email digests can be created for instrumented databases , servers and analytics as well as for applications. Where not otherwise qualified, this documentation describes the features as they are applied to instrumented applications because these use cases offer the richest set of features and choices for configuration. Alert and Respond features for other AppDynamics products are more limited.

The policy triggers for applications can be health rule violation events or a variety of other types of events. The policy triggers for databases , servers and analytics must be health rule violation events,

The types of actions that you can create for an application include notifications, diagnostics, remediation, HTTP requests, custom actions and cloud auto-scaling. The types of actions that you can create for a database , server or analytics are limited to notifications, HTTP requests and custom actions.

The types of entities affected by a health rule are more limited limited for databases , servers and analytics than for applications.


By default these roles are account owner and administrator, although custom roles could be created that include some of these permissions. For example, an account owner or administrator could create an email template manager role that could be assigned to other users to give them the ability to create and modify email templates.

TBD? In addition, custom roles could be configured with view template permission. For example, an account manager could create an HTTP request template user role that allows users to view templates without being able to modify them. This would enable power users creating HTTP actions to examine the contents of the templates that might be appropriate to their needs.

Policies, health rules, actions and email digests are application-level features. The scope of these features is the application in which they were created. Only roles with application-level permissions are required to create and manage these items.