You can read app metrics metadata to identify which Operations Manager product generated the metrics, and to retrieve other information about the metrics source.

For example, you might want to distinguish between metrics coming from apps hosted by VMware Tanzu Platform for Cloud Foundry (Tanzu Platform for Cloud Foundry) itself and apps hosted by an 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 Operations Manager tile. You can use this GUID to identify which tile deployed the Diego Cells generating the metrics.

Human-friendly metadata

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

The tags are:

• product: The value of this tag is always VMware Tanzu Platform for Cloud Foundry for the Tanzu Platform for Cloud Foundry tile. The tags for other products are: Isolation Segment, Small Footprint VMware Tanzu Platform for Cloud Foundry, and VMware Tanzu Platform for Cloud Foundry 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 Tanzu Platform for Cloud Foundry. However, for VMware Tanzu Platform for Cloud Foundry [Windows] (Tanzu Platform for Cloud Foundry [Windows]) and 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.