Properties that control the runtime MetricNodes hierarchy composition:

• PathFormat: Semicolon-separated list of local CDPTag short names. For each tag, the in-force value is taken at each measure path (nearest overshadow match). If all measure paths agree on a non-empty value, that value is used as a folder segment; otherwise the in-force value at the group's shared parent is used. Empty values are skipped.
• CollisionPathFormat: Semicolon-separated list of local CDPTag short names used when PathFormat produces no segments.
• CountedTags: Semicolon-separated list of local CDPTag short names that are allowed to have multiple values at the same level. Segment collisions are disambiguated by suffixing an occurrence number.
• CountFormat: Printf-like format (default "%d") used to render the occurrence number suffix for tags listed in CountedTags.

PathFormat Examples

PathFormat maps tag values to folder segments under the MetricNodes root. The semicolon order defines the folder order.

Example 1 - simple, non-colliding path:

PathFormat: location;equipment;metric
Output: MetricNodes.deck.crane.drive

Example 2 - disambiguation with CountedTags:

PathFormat: location;equipment;motor;metric
CountedTags: motor
CountFormat: "_%02d"
Output (two motors with motor=drive, metric=torque, and location/equipment as above):
  MetricNodes.deck.crane.drive_01.torque
  MetricNodes.deck.crane.drive_02.torque

If all PathFormat tags resolve to empty values for a group, the system tries CollisionPathFormat. If that is also empty, the MetricNode is placed directly under the MetricNodes root.