This page provides an overview of wildcards in AppDynamics. 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.

The wildcard feature is supported for metrics in the Hardware Resources, JVM, and CLR branches of the metric hierarchy. The wildcard features is only supported for custom metrics that are created with a monitoring extension as described in Extensions and Custom Metrics.

To use wildcards:

  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 Controller UI, hover over a metric in the Metric Browser to get the full metric path. Right-click the metric to view the Copy Full Path option. 

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 panel 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, tiers, or nodes of the metric that you want to select.

Use the category in the Metric Selection panel as the first segment of the relative metric path, truncating everything from the full metric path that comes before that segment. In the example, the first segment would be Agent, Hardware Resources, JVM, or CLR.

Metric Selection Category

As per the preceding example, the full metric path copied from the Metric Browser is Application Infrastructure Performance|ECommerce Server|Hardware Resources|Disks|dev-dm-1|% CPU Time. 

Truncate everything to the left of the category selected in the Metric Selection panel that is, Hardware Resources in this example, as the display in the embedded Metric Browser starts with Hardware Resources.

The relative metric path is: Hardware Resources|Disks|dev-dm-1|% CPU Time.

Consider another example where the full metric path copied from the Metric Browser is: Application Infrastructure Performance|ECommerce Server|Individual Nodes|ECommerceAppNode|Hardware Resources|Disks|dev-dm-1|% CPU Time.

The relative metric path after truncating everything to the left of the Hardware Resources is: Hardware Resources|Disks|dev-dm-1|% CPU Time.

Modify the Relative Metric Path

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:

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: Hardware Resources|Disks|*|% CPU Time. 

An Asterisk at the end of a relative path is not supported. 
For example, "Hardware Resources|Disks|C|*" is not supported. 

Configure the Metric for Multiple Entities

In the Metric Selection panel for the dashboard widget or health rule, you can configure metric for multiple entries.

To configure the metric for multiple entities:

  1. Select Specify Relative Metric Path on the bottom of the Metric Selection panel.
  2. Paste the modified, wild-carded relative metric path and click Select Metric.

Verify the Metric Specification

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

Metric Specification

Wildcards Replace Entire Path Segments

An asterisk replaces the entire segment in the path. You cannot use it to replace only a portion of a string because they are used in regular expressions.

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

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

Specify Average Response Time (ms) to get ART for all the business transactions on the ECommerce Server.

Colons in the Metric Path

The colon, if any, in the metric path is translated into a pipe. Only one segment is allowed between pipes. The colons and pipes can be used interchangeably.

For example:

The colon in the metric path, Application Infrastructure Performance|ECommerce Server|JVM|Memory:Heap|Committed (MB) is translated to Application Infrastructure Performance|ECommerce Server|JVM|Memory|Heap|Committed (MB).

For the relative metric path, to get metrics for both heap committed and non-heap committed, specify JVM|Memory|*|Committed (MB). Do not specify JVM|*|Committed (MB).