Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor edits

...

  • Determine the values or ranges that are normal for a particular metric
  • Set meaningful thresholds on which to base and receive relevant alerts
  • Determine what is a "'normal" ' metric when the application or infrastructure undergoes change

...

The AppDynamics platform automatically calculates dynamic baselines for your metrics, defining what is "'normal" ' for each metric based on actual usage. Then the platform uses these baselines to identify subsequent metrics whose values fall out of this normal range. Static thresholds that are tedious to set up and, in rapidly changing application environments, error-prone, are no longer needed.

...

AppDynamics uses dynamic baselining to establish what is considered normal behavior for your application automatically. Then you can set up health rules against those standard baselines (or use other health indicators) to track non-optimal conditions.  A health rule might be "'create a critical event when the average response time is four times slower than the baseline."'

Policies allow you to connect such problematic events (like the health rule critical event) with actions, that can, for example, trigger alerts or remedial behavior, addressing the system's issues before your users are affected. 

...

  • Business Transaction response time is much higher than normal: Defines a critical condition as the combination of an average response time higher than the default baseline by three standard deviations and a load greater than 50 calls per minute. This rule defines a warning condition as the combination of an average response time higher than the default baseline by two standard deviations and a load greater than 100 calls per minute.
  • Business Transaction error rate is much higher than normal: Defines a critical condition as the combination of an error rate greater than the default baseline by three standard deviations and an error rate higher than ten errors per minute and a load greater than 50 calls per minute. This rule defines a warning condition as the combination of an error rate greater than the default baseline by two standard deviations and an error rate greater than five errors per minute and a load greater than 50 calls per minute.

...

  • Monitoring Extensions add metrics to the existing set of metrics that AppDynamics agents collect and report to the Controller. These can include metrics that you obtain from other monitoring systems. They can also include metrics that your system extracts from services that are not instrumented by AppDynamics, such as databases, LDAP servers, web servers, or C programs. To write specific monitoring extensions, see Extensions and Custom Metrics.
  • Alerting Extensions let you integrate AppDynamics with external alerting or ticketing system and create custom notification actions. To learn how to write speicialized specialized custom notification see Build a Custom Action. Also, see Email Templates and HTTP Request Actions and Templates
  • Performance testing extensions consist of performance-testing extensions, such as the one described on Integrate AppDynamics with Apica.
  • Built-in integration extensions are bundled into the AppDynamics platform and only need to be enabled or configured. These include:

For creating your own custom extensions and integration components for AppDynamics, see the AppDynamics API information. 

...