Skip to end of metadata
Go to start of metadata

In a custom dashboard widget or health rule, you can use a wildcard to specify a metric that evaluates across several entities, such as multiple hardware entities or memory pools. This feature is supported for metrics in the Hardware Resources, JVM, and CLR branches of the metric hierarchy and for custom metrics created with a monitoring extension as described in Extensions and Custom Metrics.

To do this, you need to:

  1. Define the relative metric path to the metric that you want to display. This involves getting the full metric path in the Metric Browser and then trimming it.
  2. Modify the relative metric path to apply to multiple entities.
  3. Paste the modified relative path in the metric selector for the widget or health rule that you are configuring.

Define the Relative Metric Path

A metric path is a pipe-delineated path to a specific metric. In the AppDynamics UI, you can see the metric path of any single metric by hovering over it in the Metric Browser.

You can copy the full metric path to the clipboard by right-clicking and selecting Copy Full Path.

To define the relative metric path, truncate the leftmost part of the full metric path.

To know how much to truncate for a particular use case, look at the embedded metric browser in the Metric Selection window of the widget or health rule configuration that you are setting up. By the time you have reached this selector you will have configured the application, tier(s) or node(s) of the metric that you want to select. Use the category in the Metric Selection window as the first segment of the relative metric path, truncating everything from the full metric path that comes before that segment. In the example below the first segment would be Agent or Hardware Resources or JVM or CLR.

Using the previous images as an example, if the full metric path copied from the Metric Browser was:

Application Infrastructure Performance|ECommerce Server|Hardware Resources|Disks|dev-dm-1|% CPU Time

and the display in the embedded metric browser starts with Hardware Resources, truncate everything to the left of Hardware Resources.

The relative metric path should then be:

Hardware Resources|Disks|dev-dm-1|% CPU Time

Modify the Relative Metric Path

You can replace a single segment in the relative metric path with an asterisk to indicate that the metric should be evaluated for all the entities represented by that segment. Multiple asterisks in a single metric path are not supported.

For example, if the relative metric path is:

Hardware Resources|Disks|dev-dm-1|% CPU Time

and you want to display or create a health rule condition on the % CPU time for all of the disks in that tier or node, substitute the asterisk for the disk name as follows:

Hardware Resources|Disks|*|% CPU Time

Configure the Metric for Multiple Entities

Back in the Metric Selection window for the dashboard widget or health rule:

  1. Scroll down to the bottom of the window.
  2. Select the Relative Metric Path radio button.
  3. Paste the modified, wild-carded relative metric path in the text field.
  4. Click Select Metric.
  5. In the outer window, click Save.

Verify The Metric Specification

When you configure a relative metric specification for multiple similar entities in a custom dashboard, you see the multiple metrics displayed in the widget.


Wildcard replaces entire segment

The asterisk is used to replace the entire segment in the path. It is not used, in this feature, to replace a portion of a string as if it were a regular expression.

For example, the following usage in an attempt to get the ART for all the business transactions beginning with "View", is not valid and will generate an error:

Business Transaction Performance|Business Transactions|ECommerce Server|View*|Average Response Time (ms)

That functionality is not supported.

You can however specify

*|Average Response Time (ms)

to get ART for all the business transactions on the ECommerce Server.

Colon in metric path

If there is a colon in the metric path, the colon is translated to a pipe and there can only one segment between pipes. For example, if you have:

Application Infrastructure Performance|ECommerce Server|JVM|Memory:Heap|Committed (MB)

this is translated to

Application Infrastructure Performance|ECommerce Server|JVM|Memory|Heap|Committed (MB).

For the relative metric path, if you wanted to get metrics for both heap committed and non-heap committed you should specify:

JVM|Memory|*|Committed (MB)


JVM|*|Committed (MB).


  • No labels