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.

...

Performance is deteriorating in one business transaction so you want to view snapshots for that one transaction.

Image Modified

Alert when an app agent stops reporting to the Controller.

Create a node health rule based on the value of the Availability metric reported by the agent. If Availability is less than 1, the agent is not reporting.

...

Alert when certain business transactions' 95th percentile metrics reache a certain value.

You want to apply this rule only to business transactions with names beginning with "User".

Image Added

You do not want to create a separate health rule for every business transaction. Instead of specifying a simple metric from the metric tree, you specify a relative metric path. The health rule is evaluated for each business transaction. Use a relative metric path when you need to evaluates a single metric for multiple entities.

...

You create a health rule for one service and then copy it. Then you create different policies in IncreasePoolin which you can pair each copy of the health rule to an alert addressed to the appropriate team.

Image Added

Start a script to change the size of the connection pool

...

.

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.

Image Added

Products that Alert and Respond

...