With tagging visibility in Vantage, you can view your provider tags and create and manage virtual tags.
  • Provider tags: Tags that are directly associated with and managed within your cloud service providers, such as AWS, Azure, or GCP. These tags are typically applied to resources in your cloud environment to organize and categorize costs. Vantage retrieves and displays these tags in reports, which allows you to analyze costs based on existing tagging strategies.
  • Virtual tags: This feature can help to increase tagging coverage across your cloud infrastructure. Create cost allocation tag keys with a set of corresponding values and filters directly in the Vantage without needing to involve your engineering team in making infrastructure changes. All provider integrations in Vantage are supported, including providers that don’t natively support tags. Virtual tags are available for filtering and aggregating on all Cost Reports and cost allocation segments. They can also be used in filter criteria on saved filters.

​
Tag Management: Provider and Virtual Tags

On the Tags page, you can view all tags, including both provider and virtual tags. From the top navigation, click Settings. On the left navigation, under General Settings, click Tags. Two tabs are displayed: All Tags and Virtual Tags.
  • On the All Tags tab, you can view both your provider (denoted by a grey tag icon) and virtual tags (denoted by a purple tag icon). Tags are listed along with any associated providers. You can also hide or unhide a tag and view a corresponding Cost Report filtered to that tag (see sections below).
    • If you select a provider tag in this view, a new screen to create a virtual tag with the same name is displayed. You may want to do this in cases where you want Vantage to combine filter criteria from different providers but use the same tag name.
    • If you select a virtual tag in this view, the virtual tag page is displayed, where you can edit any existing tag criteria.
  • On the Virtual Tags tab, you can view a list of all created virtual tags. A link to the virtual tag is provided. The Tag Values column indicates how many values are currently associated with the virtual tag. Any associated providers are listed, as well as when the tag was created and who created the tag in Vantage.
At the top of the main Tags screen, you can search for specific tags and filter for tags by provider (e.g., AWS).

​
View Tags on a Cost Report

From the Tags page, you can view a Cost Report that is filtered and grouped based on a selected tag. You can do this for both provider and virtual tags. This can help you to view any current or past costs associated with the tag. In the below visual example:
  • The user searches for the environment virtual tag and selects to view a Cost Report for that tag.
  • The Cost Report is displayed. The report is also filtered by the tag’s associated providers by the tag and grouped by that tag’s values.

​
Hide Tags

From the Tags page, you can hide tag keys that you don’t want to appear in report filters or grouping options. This is useful for removing redundant tags or preventing other users from seeing certain tags in reports. To hide a tag key, click the eyeball icon next to the tag on the All Tags tab. As soon as a tag key is hidden, the following changes occur in Vantage:
  • Hidden from report menus: The tag key is no longer displayed in the Filters or Group By menus on reports for other Vantage users; however, users with the Owner role can still manage tag visibility (i.e., unhide the tag) via the Tags screen.
  • Existing reports remain functional: If a report was already filtered or grouped by the hidden tag, it will continue to work, but if you edit the report’s filters, the hidden tag will no longer be available in the filter’s selection list.
  • Usable in virtual tags: Hidden tags can still be used when creating virtual tags and will appear in virtual tag filters. If a hidden tag is included in a virtual tag’s filter criteria, a message is displayed next to it, indicating that it is hidden and only usable for virtual tag creation.
  • Still accessible via API: Hidden tags remain available through API requests.

​
Hide Tags Example: Standardizing Redundant Tag Keys

You are working to clean up your tagging and notice that teams have applied multiple variations of the same environment-related tag key across different AWS resources:
  • env
  • environment
  • Environment
Because all three tags represent the same concept, having them appear separately in report filters and grouping options creates inconsistencies and makes cost analysis more difficult. You are unable to see the full view of how costs are attributed to each environment. You complete the following steps to hide the redundant tags:
  • You navigate to the Tags page in Vantage to search for and identify the different versions of the environment tag. You then hide each iteration of this tag so that you can create a new standardized version of the tag with Vantage virtual tags.
New virtual tag that shows all iterations of environment
  • All three hidden tags no longer appear in the Filters and Group By menus for other users.
Attempting to filter for a hidden tag
  • Existing reports that were already filtered or grouped by these tags remain functional; however, if a user edits the report’s filters, they will no longer see those hidden tag variations.
  • The hidden tags are still available via API requests, so any external automation using them still continues to work.
You then complete the following steps to create a virtual tag that combines the values from all the previous tag iterations:
  • You create a new virtual tag named environment that consolidates all three variations from the AWS provider tag.
  • For each tag value (e.g., production or development), you create a filter that combines the production values from the previous tags. You can then use this new virtual tag within reports.
New virtual tag that shows all iterations of environment
As a result, your users now see only the environment virtual tag in their report filters, reducing confusion and keeping reports standardized. This approach helps enforce tagging consistency without you having to further educate your users on which versions of a tag key to use in reports.

​
Virtual Tags

To get started with virtual tagging, you can also view a video demo on Vantage University .

​
Virtual Tags vs. Saved Filters vs. Cost Allocation Segments

Virtual tags can be considered foundational to the rest of the data within Vantage. They should remain fairly static, and changes should be considered delicate. These changes will flow across all data and apply to all workspaces. The most common tag keys will be items like team, cost center, and environment. Segments can then be used to create different hierarchical views for tagged data. This feature is useful for breaking down the data by different perspectives, such as by cost center or by OPEX/CapEX. Saved filters can then be used in a more ad-hoc fashion to add lenses on top of base data. For instance, you could create a saved filter just for North America that standardizes a set of regions across providers and can be used by teams on their reports or dashboards without having to know the set of filters needed to create the list of regions. When new regions come online, it’s easy to modify the saved filter to include this region.
If you want to transition any of your cost allocation segments to virtual tags, contact support@vantage.sh.

​
Custom Value Tags

With custom value tags, you can create new cross-provider cost allocation tags to help better your tagging strategy. For example, you may have a series of resource tags, by product, across each of your providers. You can create custom tags in Vantage to combine those costs into one unique product tag for all resources in that product group. See the example section below for details.

​
Cost-Based and Business Metrics-Based Allocation Tags

The cost-based and business metrics-based allocation tag types allow for dynamic cost allocation, which is the process of allocating costs based on another existing cost or metric. See the below video for an introduction to dynamic cost allocation.

​
Cost-Based Allocation Tags

With cost-based allocation tags, you can create a dynamically allocated cost structure. Select a set of input costs (e.g., all AWS costs), an existing cost tag to use for allocation (e.g., a teams cost tag), and an output cost (e.g, a static cost, like AWS Support) that you want to be allocated the same way as your input cost. See the example section below for details.

​
Business Metrics-Based Allocation Tags

With business metrics-based allocation tags, you select an existing business metric (e.g., CPU use per product) and indicate your output cost (e.g., all GCP Compute costs) so that the allocation of the output cost mimics the percentage allocation of the existing business metric. See the example section below for details.

​
Virtual Tags Limit

You can create up to 50 virtual tag configurations, with each tag supporting up to 100 configuration values.

​
Create Virtual Tags

This feature requires Owner permissions in Vantage. See the Role-Based Access Control documentation for details. Virtual tags apply to all workspaces.
1

From the top navigation, click Settings.
2

From the side navigation, under General Settings, click Tags.
3

On the All Tags tab all your tags—both provider and virtual—are displayed. Click the Virtual Tags tab. All existing virtual tags are displayed. You can edit any existing tags from this tab. To add a new virtual tag, click Create a Virtual Tag.
4

Enter a title for the Tag Key.
5

For Billing Period Backfill, select a billing period (e.g., Apr 2024) for which the tag should be backfilled.
6

Enable the Can Override toggle if you want the virtual tag to override an existing service cost value. For example, if you create a virtual tag that conflicts with an existing provider tag, this option will override the existing provider tag key in Vantage reports.
7

In the Values section, click +Add. Select whether you want to create a Custom Value, Business Metric, or Cost Based value. Click through the tabs below for instructions on each value type.
You cannot use an existing virtual tag within the filters for virtual tags with forms of cost allocation (i.e., Business Metric or Cost Based virtual tags). You can, however, select an existing provider tag (e.g., one that comes from AWS). If you attempt to select an allocated virtual tag as part of your filter criteria, the following message is displayed.
A message in a virtual tag filter indicating you cannot use allocated virtual tags for filter criteria in another tag
You can use existing virtual tags in the Output Costs Filter for Custom Value virtual tags. See the Nested Virtual Tags section for details.
1

Click Assign Custom Value.
2

Enter a Tag Value title. Titles can contain only letters, numbers, and the following characters: \_ - & + , . : / \ @. You cannot use saved filters to define a virtual tag value’s filters.
3

Specify the tag value’s filter criteria (i.e., Output Cost Filters). These filters function just like filters on Cost Reports and cost allocation segments. For information on how to create detailed filters, see the Cost Reports documentation.
8

At the top, click Save.
Processing tag changes usually takes under an hour. At the top of the Virtual Tags screen, the processing status is displayed. Processing times vary based on the number of tags and volume of data you have imported into Vantage.
The virtual tag screen with a processing status displayed for Fastly and New Relic

​
Nested Virtual Tags

With nested virtual tags, you can use virtual tags as part of the filter criteria for other virtual tag values. Nested virtual tags apply only to Custom Value Virtual Tags. These tags let you align cloud provider data with internal taxonomies for effective grouping and querying. To reference an existing virtual tag in another virtual tag:
1

Create a new Custom Value.
2

Enter a name.
3

For the Output Cost Filter:
  • Select a provider.
  • Select Tag, then select an existing virtual tag key. Look for the purple tag icon with the Vantage logo to identify existing virtual tags.
The virtual tag screen selecting an existing virtual tag in the filter for a new tag value

​
Nested Virtual Tag Considerations

  • Do not create a nested virtual tag that references itself (i.e., a cyclical reference); this will result in an error.
  • If you update the filters of a virtual tag that is referenced by another virtual tag, costs are reprocessed based on the updated hierarchy.
  • If you delete or rename a virtual tag that is referenced by another virtual tag, you will see a warning. If you proceed, Vantage reprocesses costs with the new configuration.
Modal that's displayed indicating if you delete a nested virtual tag that it will affect other connected tags
  • You can create up to 49 nested virtual tags, since an organization is limited to 50 distinct virtual tag keys. Because nested virtual tags are processed sequentially, increasing the number of nested values will slow down the tagging process.
See the Nested Virtual Tags Example section below for a sample tag hierarchy.

​
Virtual Tag Order

Tag values are arranged in priority order on the Virtual Tags screen. You can move tag values up and down in the UI to reorder them, as demonstrated in the visual example below.
GIF of two tag values, staging and production, being reordered in the Tags UI
When cost data is ingested into Vantage, the first value that matches the corresponding filters will be applied to that line item. In cases where filters overlap, the order of tag values within each key determines the value that is applied.

​
Filter and Group by Virtual Tags

You can filter by virtual tags in Cost Reports, cost allocation segments, and when creating saved filters. Virtual tags are visible along with your existing provider tags. Use the Tag (Label in GCP) filter and grouping option.
A Cost Report filter with two filters applied: one for AWS costs for the team/data tag and one for GCP costs with the same tag

​
Delete a Virtual Tag

To delete a virtual tag, navigate to the Tags page. Select the Virtual Tags tab and open an existing virtual tag. Click the trashcan icon at the top of the tag page. Your data will be re-tagged, excluding the deleted virtual tag, going back to the deleted tag’s backfill bill period. Newly ingested data will no longer be tagged with the deleted tag.

​
Virtual Tagging Examples

The following examples demonstrate how to use virtual tagging in a multi-provider organization.

​
Custom Values Examples

​
Example 1 - Cross-Provider Tagging

You want to create a tag mapping for each of your teams that maps corresponding teams with certain services and provider accounts.
1

Create a New Tag

You create a tag key called Teams.
The Tag Key field displayed in the Virtual Tags UI; the name Teams is entered
2

Add Tag Values and Filters

You add the corresponding set of virtual tag values and filters:
  • The data team tag value corresponds with a filter for all costs for GCP BigQuery and Amazon Redshift.
  • The mobile team tag value corresponds with a filter for its related GCP projects and AWS accounts.
  • You continue this pattern and create similar values with corresponding filters for your other teams.
A sample Tag Value field for a value of data with filter for Service of BigQuery and Amazon Redshift
A sample Tag Value field for a value of data with a filter for GCP Project of mobile and AWS account of mobile
Within Cost Reports, you can easily filter and group by these tag options to easily see costs for an individual team. In the below visual example, the Cost Report is grouped by the team tag, and the mobile and data values are displayed along with the other team tag values you created.
A sample Cost Report grouped by Tag showing a mobile and data tag

​
Example 2 - Consolidate Existing Tags

You have a tagging practice established at your organization, but teams often create tags with spelling variations, tags with typos, or they create duplicate tags. For example, the data team has resources tagged with data, Data, and data-prod. This is an issue across many of your teams. You want to consolidate all these tags, across providers, into one data tag.
1

Create a New Tag

You create a tag key called Teams to override existing tags.
The Tag Key field displayed in the Virtual Tags UI; the name Teams is entered
2

Add Tag Values and Filters

You add the corresponding set of virtual tag values and filters. In this example, all permutations of the data team tag are combined into one virtual tag.
A sample Tag Value field for a value of AWS team tags equaling data, data-prod, and Data. Another value for a GCP team Label equaling data
Within Cost Reports, you can easily filter by this tag to see all costs related to the data team. This saves you the work of needing to always filter for all permutations of this tag. Now, you need to filter by only one tag.
A Cost Report with a filter for AWS and GCP team tag of data

​
Example 3 - Using Flexible Match to Consolidate Similar Tag Values

Your teams use inconsistent tagging conventions, resulting in multiple variations in casing and formatting. For example, Team A’s tag appears in several forms across usage data, such as teamA, team_a, team-a, and Team A. You can use the flexible match filter option to match for all of these variants, as well as future variants, in a single tag configuration.
1

Create a New Tag

You create a tag key called Teams to override existing tags.
The Tag Key field displayed in the Virtual Tags UI; the name Teams is entered
2

Add Tag Values and Filters

Create a virtual tag configuration for Team A. For the Output Cost Filters, use the Teams flexible match to the string Team A.
A sample Tag Value field for a value of AWS Team tag flexible matches Team A
This will automatically match all variants of Team A, such as teamA, team_a, team-a, and Team A .

​
Cost-Based Allocation Example

In your organization, teams share resources, such as RDS databases or EC2 instances, and each team consumes different percentages of these resources each month. Your organization is also charged a static support fee each month for AWS. As shown in the diagram below, you want to allocate a portion of the support fee to each team based on their proportional use of AWS resources. So in the below example, since the Infra team is responsible for 50% of all AWS costs, they should also be responsible for 50% of the support fee. You can create a cost-based allocation virtual tag for allocating portions of the support fee to each respective team.
A flowchart that has the AWS logo in a block at the top. AWS has three arrows pointing to tag icons that say Infra 50%, Mobile 20%, and Data 30%. These tags point to a box that says Dynamic Cost Allocation with the icon for AWS Support. This box has three arrows that point to three boxes. The boxes say Infra Team AWS Support Costs 50%, Mobile Team AWS Support Costs 20%, and Data Team AWS Support Costs 30%.

​
Prerequisites

You have an existing provider tag in AWS that identifies resources for your teams. This tag will be used in step 2.
1

Create a New Cost-Based Allocation Tag

  • Navigate to Settings > Virtual Tags.
  • Create a new virtual tag.
  • Select the Cost-Based option for the tag value.
2

Select an Input Cost Filter

For your input cost, select All AWS Costs. Set an additional filter for the Usage charge type to filter on only usage-related costs. This filter will ignore costs related to items like credits, taxes, fees, etc.
3

Select a Tag Key

You select your existing teams tag key you have in AWS that will be used for allocating costs.
4

Select an Output Cost Filter

In this example, since your infrastructure team is responsible for 50% of all AWS costs, the mobile team for 20%, and the data team for 30%, you can mimic this allocation across another static cost, or your output cost. Select the filters for the AWS support fee.
A sample Tag Value field for AWS Support Fee costs
Once the tag is created, create a new Cost Report and add the following criteria:
  • Create a filter for AWS Support costs.
  • Add grouping criteria to group by your new cost-based dynamic allocation tag.
The resulting report shows how much of the support fee each team is allocated.
A sample Tag Value field for AWS Support Fee costs

​
Business Metrics-Based Allocation Example

You are working with your infrastructure team and want to ensure that the proportional cost of CPU time on a shared resource is allocated to the distinct cost centers that are consuming the CPU. In the below example, you want each team’s portion of CPU usage billed as a corresponding percentage of the overall Namespace CPU cost. So, if Team A uses 30% of the resource’s CPU, then they should be billed a proportional percentage of the total Namespace’s costs.
A flowchart that has a CPU icon in a block at the top and says Shared Resource CPU. CPU has two arrows pointing to two boxes with people icons that say Team A CPU Usage and Team B CPU Usage. These boxes point to a box that says Total Namespace Costs with the Kubernetes icon. This box has two arrows that point to two boxes that say Portion of Namespace Costs Allocated to Team Based on Portion of CPU Usage.

​
Prerequisites

To determine the cost of CPU time to allocate to each respective team, you first create a labeled business metric that includes the CPU time labeled by team. Vantage then calculates the respective percentage of CPU time for each team. The labeled business metric has the following format. 
date,amount,label
2024-01-09,825,teama
2024-01-09,600,teamb
2024-01-10,500,teama
2024-01-10,200,teamb
2024-01-11,723,teama
2024-01-11,456,teamb
1

Create a New Business Metrics-Based Allocation Tag

You create a new business metrics-based tag:
  • Navigate to Settings > Virtual Tags.
  • Create a new virtual tag.
  • Select the Business Metric option for the tag value.
2

Select the Labeled Business Metric

Search for and select the labeled business metric you just created to use for allocation.
3

Select an Output Cost Filter

Select the Vantage costs that will be split based on the percentages calculated in your business metric. In this case, you select a filter to show costs for the specific Namespace you want to be allocated.
A sample Tag Value field for specific Kubernetes namespace costs
Once the tag is created, create a new Cost Report and add the following criteria:
  • Create a filter for the specific Namespace.
  • Add grouping criteria to group by your new business metrics-based dynamic allocation tag.
The resulting report shows how much of the Namespace costs each team is allocated.
A sample Tag Value field for AWS Support Fee costs

​
Nested Virtual Tags Example

You want to maintain a hierarchy that reflects how your business units are associated with various applications, and track costs of all your applications per business unit over time. In addition, you also want to avoid having to manually update multiple virtual tags whenever an application changes ownership to another business unit, so you aim to set up a dynamic structure that’s automatically updated.
1

Create an Application Virtual Tag with Values for Each App

You create a new tag called Applications:
  • Each value represents a specific application (e.g., app1, app2, app3, app4).
  • The filters for each value are AWS costs related to specific resources, like RDS or EC2 instances.
An example of an application tag based on specific AWS resources
2

Create a Virtual Tag for Business Unit Costs

Next, you define a virtual tag for Business Units:
  • Each value represents a specific business unit (e.g., Core Production, Core Development).
  • Each filter uses the preexisting Applications virtual tag you just created to associate specific apps with the corresponding business unit. Notice that virtual tags are denoted by a purple Vantage tag icon to differentiate them from provider tags (gray icon).
An example of a business unit tagged associated with an existing application tag
3

Review the Nested Virtual Tag in Reports

In associated reports, you can track all costs per business unit, knowing that each business unit comprises a set of corresponding apps. If an app ever changes its associated business unit, you need to update only the filter criteria on the Business Units virtual tag, and all other costs will be processed accordingly. The below report is grouped both by business unit and application to show the total breakdown.
An example Cost Report with the Applications and Business Unit tag groupings

​
Tagging Untaggable Resources in AWS Example

While you can apply cost and metadata tags in AWS to many resources, there are many other resources that are untaggable in AWS. Therefore, it is hard, if not almost impossible, to achieve 100% allocation in AWS alone. One quick way to first get an inventory of all untagged resources in Vantage—regardless of if they are untaggable—is to create a Cost Report with the following filters:
  • Provider is AWS
  • Where Not Tagged with Any Key
Untagged cost filters
Then, add grouping criteria for Service and Category to get a view of the types of resources that are currently untagged. If these resources are taggable in AWS, you can add cost allocation tags there and see those tags represented in Vantage when you filter or group by specific tag.
See the AWS documentation for more information on what you can tag directly in AWS.
Untagged cost filters
Many services and resource categories, however, cannot be tagged in AWS. You can use virtual tags to create tags in Vantage for these untaggable resources. In the table below, the Vantage Resource Filters column represents the filters you can set as the Output Cost Filters in the virtual tag configuration. For example, if you want to tag S3 Data Transfer for specific resources, you could use the following filter criteria.
Untagged cost filters
AWS ResourceDescriptionVantage Resource Filters
Elastic IPsAccording to AWS, “You can tag an Elastic IP address that’s allocated for use in a VPC, however, cost allocation tags are not supported.”Provider: AWS Subcategory: Amazon Virtual Private Cloud contains inuse
CloudWatch MetricsCloudWatch Metrics involve performance data from AWS services, which are not taggable and are used for monitoring and alerting.Provider: AWS Category: AmazonCloudWatch is Metric Further filter by resource ID
S3 Data TransferData transferred in and out of S3 buckets, which is tracked but not taggable.Provider: AWS Category: Amazon Simple Storage Service is Data Transfer Further filter by resource ID
QuickSight resourcesResources within Amazon QuickSight, such as dashboards and analyses, which do not support tagging.Provider: AWS Service: Amazon Quicksight Optional detailed filters for Category (e.g., Business Analytics) or individual resource ID
CloudSearch resourcesAmazon CloudSearch domains and their configurations, which are untaggable.Provider: AWS Service: Amazon CloudSearch Optional detailed filters for Category (e.g., Data Transfer, Search Instance) or individual resource ID
EBS Snapshot CopyAmazon EBS Snapshots that are copied between regions for Disaster Recovery or restore purposesProvider: AWS Service: Amazon Elastic Block Storage (EBS) Category: Storage Snapshot Further filter for resource ID