For many large-scale cloud environments, the VMware Tanzu CloudHealth platform collects over 150,000 unique tag keys per cloud. Tanzu CloudHealth collects and reports on all tag keys, regardless of whether they are being used. Processing a large number of tag keys while generating a report can negatively impact performance and usability, but the Tag Management feature overcomes these issues by processing and reporting only those tag keys useful to you.
In the Tanzu CloudHealth platform, from the left menu, select Governance > Tag Management. The Tag Status section displays the total number of tags that are Enabled, Disabled, Used in the Tanzu CloudHealth platform, and Not used in the platform.
The Tag Management feature provides visibility into all the tags available in your cloud environment, however the rest of the platform reports only on the tags enabled in the tag key list.
The following features are impacted when you change the tag key status on the Tag Management page:
Currently, Tanzu CloudHealth supports tags from AWS, Azure, and GCP cloud services, and Tanzu CloudHealth custom tags. Tags can also be referred to as labels in GCP.
Tags help you associate the cost, usage, performance, and other metrics of your assets with specific business groups. Tanzu CloudHealth’s Tag Management feature collects and maintains all the tag key values and provides valuable insights into the usable tags in your environment. You can have greater visibility of tag usage across your cloud environment, and the service will help you answer questions such as:
In the Tanzu CloudHealth platform, from the left menu, select Governance > Tag Management. The Tag Management page displays the tag key list with the following tag key details:
Column Name | Description |
---|---|
Tag Key | Name of the asset tag key. If the tag key is registered with multiple clouds, a separate row is displayed for each combination of cloud service provider and tag key. |
Cloud | Name of the cloud service provider (AWS/Azure/GCP) to which the tag key is registered. If you notice more than one row for the same tag key, this column will help you differentiate between those multiple rows. |
Tag Values | Number of distinct values associated with a combination of cloud service provider and tag key. |
Enabled | When checked, it indicates that tag keys are available for use in the Tanzu CloudHealth platform. When unchecked, it indicates that Tanzu CloudHealth will not use the disabled tag keys in any feature except the Tags column of your asset reports. |
Used | Indicates whether the tag key is used in any of the Tanzu CloudHealth features, such as policy, perspective, or saved report. |
Tanzu CloudHealth Tags | When checked, it indicates that the tag key is associated with Tanzu CloudHealth Custom tags. The tag key may also be associated with the Cloud Service provider tags if the same tag key exists both in the Tanzu CloudHealth custom tags and in the Cloud Service provider original tags. |
Asset count | Number of assets associated with a combination of cloud service provider and tag key. |
First discovered | Date and time when the tag key was first discovered by the Tanzu CloudHealth platform. |
Last Updated | Date and time when the tag key was last modified. The timestamp indicates one of the following tag key updates – Tag key or tag value modification, new tag value addition, enable or disable tag key, tag key assigned to an additional asset(s) or removed from an already tagged asset(s). |
Important to know
On the Tag Management page, by clicking the number of assets in the Asset Count column, you can view the breakdown of tag key by asset type. Further, on clicking the asset count on the Asset Count Breakdown table, you will be redirected to the individual asset report mapped to the given asset type.
Important to know
Tag curation is the process of identifying, managing, organizing, and filtering tag keys for your business analysis needs, thus, reporting only on the tags relevant to your business strategy. You can use the Tag Management feature as a tag curation tool and process only the tags relevant to your business needs.
For tag curation in the Tanzu CloudHealth platform, you can
On the Tag Management page, select the desired tag keys and click Bulk Actions dropdown to Enable or Disable the tag keys in the Tanzu CloudHealth platform. Note that the Tanzu CloudHealth platform will report only on the tag keys enabled in the Tag Key list.
The tags that are not used in Perspective/Report/Policies are called unused tags. By default, all unused tags are enabled in the platform. Switch the toggle for Disable unused tags to On, if you want to disable unused tags in the platform.
Note
You can use filters to find specific tag keys. The filtered tag key list can help in your tag usage analysis.
On the Tag Management page, click Filters. Select your filter choices and click Apply. You can filter the tag key list using the following filter options:
Filter option | Description |
---|---|
Cloud | Select the cloud environment (AWS/Azure/GCP) for which you want to view the tag key list. |
Is Enabled? | Select to view only the enabled or disabled tags in the tag key list. |
Includes Tanzu CloudHealth Tags? | Select True to view the tag keys with Tanzu CloudHealth custom tags. |
Is used in reports? | Select True to include tag keys currently used in Tanzu CloudHealth perspectives, policies, or saved reports. |
Discovered after and Discovered before | Select a date range or a single date to view the tag keys included in the tag key list for the selected duration. |
Updated after and Updated before | Select a date range or a single date to view the tag keys updated in the tag key list for the selected duration. |
Based on your filter criteria, you will see a specific subset of tag keys instead of all the tag keys available in the platform.
Missing tags may have been disabled in the Tag Management feature. Enable the tags to view it in Perspectives.
In Policies
In Perspectives
In Asset Reports
In Saved Reports
A tag key with leading whitespaces is considered different from a tag key with the same label without leading whitespaces. However, a tag key with trailing whitespaces is treated the same as a tag key with the same label without trailing whitespaces.