Identifying the Source Deployment of Metrics
Page last updated:
Warning: VMware Tanzu Application Service for VMs (TAS for VMs) v2.9 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic explains how to read app metrics metadata to identify which Ops Manager 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 VMware Tanzu Application Service for VMs (TAS for VMs) itself and apps hosted by an Isolation Segment deployment.
Metrics identify their source deployment with a
deployment tag followed by
cf- prefixed to the GUID of the source Ops Manager tile. You can use this GUID to identify which tile deployed the Diego Cells generating the metrics.
TAS for VMs 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 Application Servicefor the TAS for VMs tile. The tags for other products are:
Small Footprint VMware Tanzu Application Service, and
VMware Tanzu 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
nullfor TAS for VMs. However, for VMware Tanzu Application Service for VMs [Windows] (TAS for VMs [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_tagname. 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.