This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


Versions Compared

Key

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

Related pages:

Watch these videos:

Appd noprint
iFrame
srchttps://player.vimeo.com/video/109648591?badge=0&title=0&byline=0
width300
height175
 

Alert and Respond: Quick Tour

...

  • 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.

Scope and Access to Alert and Respond Features

Typically different types of users with different types of roles set up and use different alert and respond features.

Email templates, HTTP request templates, and Email/SMS configuration are account-level features. The scope of these features, once set up, is the entire AppDynamics account. The items created at the account level are available to all the applications in that account. Account-level items are created and managed by users who have account-level roles that include permissions to create them.

Image Added

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.