FOCUS column
Tags
The key/value metadata attached to the resource or the charge, as a map of tag keys to values. Tags carry the ownership and product dimensions that containers do not, and their coverage and validity decide how much of a bill can be allocated directly. Providers store them differently; FOCUS presents them as one map.
Example
A row carries the map cost-center: 4410, product: checkout, environment: prod, which the allocation rules read to place the charge.
Where it comes from, per export
The export column that feeds Tags in each format the platform ingests, and the transform applied. A format with no row does not carry the column; the value is then absent rather than guessed.
| Export | Source column | Transform |
|---|---|---|
| AWS Data Exports, FOCUS | Tags | parsed into key/value pairs |
| Azure Cost Management, FOCUS export | Tags | parsed into key/value pairs |
| Azure Cost Details (actual cost) | Tags | parsed into key/value pairs |
| Azure Cost Details (amortized cost) | Tags | parsed into key/value pairs |
| Google Cloud detailed billing export | labels | parsed into key/value pairs |
How Runcost uses it
Runcost normalizes tag keys across providers to one owner and product key, treats invalid values as missing, and reports the resources whose tags need fixing.
Related columns
About this reference
Generated from the column contract and provider rules that Runcost runs, and written by Faisal Saleem, Founder. The normative definitions are in the FinOps Foundation’s FOCUS specification at focus.finops.org.