Virtual Tags
2 minute read
A virtual tag applies tag key/value pairs to cost rows that match conditions you define. Virtual tags enrich your cost data without changing the underlying records and without re-tagging resources in the cloud provider. They apply tenant-wide. The page provides:
- Tag mappings: Rules that pair one or more tags with the match conditions that select cost rows.
- Sub-rules: Nested mappings that refine a parent mapping for finer-grained control.
- Tenant-wide scope: Mappings apply across the tenant to standardize tagging in reports.
- Enrichment: Fill gaps where native provider tags are missing or inconsistent.
Access the Virtual Tags page
- Log in to the CloudBolt Platform.
- In the sidebar, select Settings.
- Select Virtual Tags.
- If this is your first time here, select Create Virtual Tag Ruleset. The mappings list appears once it’s created.
Virtual Tags overview
| Section | Description |
|---|---|
| Search | Filter the list by tag key or value (Search by tag key or value…). |
| Mappings list | Your virtual-tag mappings, with a count of how many are defined. Mappings can nest: use Add sub-rule to create child mappings under a parent. |
| Add Virtual Tag | Opens the dialog to create a new mapping. |
Add a virtual tag
- Select Add Virtual Tag.
- In the Tags section, add one or more Tag Key / Tag Value pairs to apply. Keys autocomplete from existing keys; duplicate keys at the same level are rejected.
- In the Match Conditions section, add the conditions that select which cost rows receive the tags.
- Save the mapping.
Each match condition is a Field, an operator, and a Value. Available operators are Equals, Not Equals, In, Not In, Greater Than or Equal, Less Than or Equal, Contains, Not Contains, and Regex. With several conditions, choose Match all or Match any. For Equals/In-style operators, values autocomplete from actual billing values.
Root-level mappings need at least one match condition.
Nest mappings with sub-rules
To refine a mapping, select Add sub-rule on it. Sub-rules create child mappings under the parent, letting you layer finer-grained tagging on top of a broader match. For example, tag everything in an account with a team, then override the tag for a specific service within that account.
Use virtual tags across the platform
Once applied, virtual tags appear throughout the platform as their own filter and group-by source. In Cost Explorer, Virtual Tags is a separate filter entry from provider Tags, and virtual tags also surface in Tag Analysis.
Changes to virtual tags take effect on the next pipeline run.