AppDynamics recommends using short metric names so that the whole name is visible when displayed in the Metric Browser. Prepend the metric path to the metric name when you upload the metrics to the Controller. Metric names must be unique within the same metric path but need not be unique for the entire metric hierarchy. See Create a directory under the Machine Agent monitors directory.Ĭopy your script file and the monitor.xml file into the new subdirectory.
Agent Configuration RequirementsĬonfirm that you have correctly configured the Machine Agent in the controller-info.xml file and on the Agent start command on the command line.
USE PROCESS MONITOR TO LOOK FOR LONG FILE NAMES FOR FREE
See the AppDynamics Exchange for free downloads. It is possible that someone has already created what you need or something close enough that you can download and use it after making a few modifications. Review Existing Extensionsīefore creating your own extension, review the extensions that have been created and shared among members of the AppDynamics community. This page describes the steps for adding custom metrics using a shell script and includes an example. The Machine Agent passes these metrics to the Controller. Your script reports the custom metrics every minute to the Machine Agent. You can write a monitoring extension script (also known as a custom monitor or hardware monitor) to add custom metrics to the metric set that AppDynamics already collects and reports to the Controller.