Related Pages:

You can create health rules using custom metrics to monitor a single entity or multiple entities.

Create Health Rule Using Custom Metrics to Monitor Single Entity

To create a health rule using custom metric to monitor a single business transaction, node, or overall application performance:

  1. When you create a health rule, specify the health rule type as custom.

  2. When you configure the conditions, in the Select Metric window, choose to Specify a Metric from the Metric Tree.
  3. Select the metric from the embedded metric browser.

Create Health Rule Using Custom Metrics to Monitor Multiple Entities

You can create a health rule that evaluates a custom metric that exists across various entities, for example across several nodes. You want to do this with one health rule; you do not want to create a separate health rule for each node. In this case, you need to specify a custom metric using the relative metric path to the metric instead of selecting the metric from the embedded metric browser.

  1. Get the custom metric path from the Metric Browser.
  2. Configure the health rule using the custom metric path as a relative path.

Get the Custom Metric Path for a Multi-Entity Metric

  1. Navigate to the Metric Browser by selecting the Metric Browser in the left navigation pane.
  2. Select the metric that you want to use for the condition.
  3. Right-click and select Copy Full Path.
  4. Save this value in a file from which you can copy it later.

The following example gets the metric path for the CPU %Busy metric for the Inventory Server tier. The CPU %Busy metric would be appropriate to use in a health rule that affects all the nodes in that tier.

Configure a Health Rule Condition That Evaluates a Custom Metric for Multiple Entities

  1. In the Overview panel of health rule wizard choose the health rule type for the kind of entity that you are monitoring.
  2. In the Affected Entities panel select the affected entity.
  3. When you create the condition component that uses the metric, in the Select Metric window choose Specify a Relative Path Metric.
  4. Crop the relative metric path that you saved from the metric browser by doing one of the following:
    • For all health rule types except Node Health-Hardware, JVM, CLR or Custom, crop the path to use the metric name along with the application name and category, for example, Custom Metrics|ECommerce Demo|Slow Query Calls|Call Count.
    • For Node Heath-Hardware, JVM, CLR and Custom health rule types, crop the path to use everything after the entity, for example, after the Node name. In the example below, the cropped path would look like this.
  5. Paste the cropped relative metric path in the relative metric path field of the Metric Selection window.
  6. Click Select Metric.

In relative metric path, you can use a wildcard to specify a metric that evaluates across several entities, such as multiple hardware entities or memory pools. See Use Wildcards in Metric Definitions. If a wildcard is used to evaluate more than one million metrics, Cisco AppDynamics disables the health rule to prevent any performance issues. While using wildcards, you must split the health rules or create multiple health rules to monitor specific metrics for a defined set of entities.