Identifying the Source Deployment of Metrics

Page last updated:

This topic explains how to read app metrics metadata to identify which Pivotal Platform product generated the metrics, and to retrieve other information about the metrics source.

For example, you may want to distinguish between metrics coming from apps hosted by Pivotal Application Service (PAS) itself and apps hosted by a Pivotal Isolation Segment deployment.

Source Deployment from Tile GUID

Metrics identify their source deployment with a deployment tag followed by cf- prefixed to the GUID of the source Pivotal Platform tile. You can use this GUID to identify which tile deployed the Diego Cells generating the metrics.

Human-Friendly Metadata

PAS and other runtime tiles tag metrics with additional metadata to help users parse metrics coming from different deployments. Downstream monitoring products such as Pivotal Healthwatch also use this metadata to display human-readable names.

The tags are:

  • product: The value of this tag is always Pivotal Application Service for the PAS tile. The tags for other products are: Pivotal Isolation Segment, Pivotal Application Service Small Footprint, and Pivotal Application Service for Windows.

  • system_domain: The value of this tag corresponds to what you set in the System domain field in the Domains pane of a given tile.

  • placement_tag: The value of this tag is always null for PAS. However, for Pivotal Application Service for Windows (PASW) and Pivotal Isolation Segment tiles, you can configure this value using the Segment name field in the App Containers pane. An operator can display capacity and other relevant metrics using the placement_tag name. This makes it easier to reason about the importance of a given segment when issues arise.

These tags are properties of the Metron agent running on each VM in a deployment.