Which path is used to specify a metric that evaluates across multiple hardware entities or...

A relative metric path with a wildcard is used when a metric condition must be evaluated across multiple comparable entities, such as hardware resources, JVM memory pools, nodes, or other dynamically named metric branches.

A relative path is resolved in the context of each entity selected by the health rule or metric evaluation scope. Adding a wildcard allows AppDynamics to match multiple child metric paths rather than requiring one fixed, fully qualified metric location. This is particularly useful when memory-pool names, hardware instances, or resource identifiers differ between nodes or runtime environments.

An absolute metric path points to one exact location in the metric hierarchy and is therefore better suited to a single, explicitly identified metric. Although wildcard matching can be supported in metric configurations, the correct approach for evaluating equivalent metrics across multiple scoped entities is the relative-path model.

The Metric Browser supports hierarchical metric navigation, and wildcard-capable paths are used where dynamic or repeated entity structures must be addressed. Relevant CAAPA Study Guide topics include Metric Browser, Relative and Absolute Metric Paths, Wildcard Metric Selection, Health Rule Conditions, Hardware Resource Metrics, and JVM Memory Pool Monitoring.