AppDynamics Application Intelligence Platform

3.8.x Documentation



Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Advantages of adding external metrics to AppDynamics include:

  • automatic baselines and anomaly detection for external metrics
  • availability for display on custom dashboards
  • availability for use in policies
  • visibility of all metrics in the Metric Browser, where you can display external metrics along with AppDynamics metrics on the same graph

You can create monitoring extensions using:

  • Java
  • HTTP Listener
  • Shell or batch scripts
  • .NET performance counters

Monitoring Extensions Using Java

Your custom metrics may be too complicated to collect using a script. For example, you may need to perform complex calculations or call a third party API to get the metrics.

In this case you can extend the JavaServersMonitor class to collect the metrics and report them to the Standalone Machine Agent. Your Java program extends the JavaServersMonitor class to provide your custom functionality.

See Build a Monitoring Extension Using Java.

Monitoring Extensions Using an HTTP Listener

You can post HTTP requests to the Standalone Machine Agent to send it custom metrics every minute. This is done by starting the Standalone Machine Agent with a Jetty HTTP listener.

See Standalone Machine Agent HTTP Listener for information on starting the HTTP listener and sending it metrics.

Monitoring Extensions Using Scripts

You can write a shell script (LINUX) or batch file (Windows) to report custom metrics every minute to the Standalone Machine Agent. The Standalone Machine Agent passes these metrics on to the Controller.

See Build a Monitoring Extension Using Scripts.

Monitoring Extensions Using Performance Counters in a .NET Environment

You can add additional performance counters to the standard hardware metrics reported by the embedded .NET Embedded Machine Agent by configuring the <perf-counters> element in the .NET Embedded Machine Agent's application.config file.

See Windows Performance Counters.

  • No labels