FOCUS column
PricingUnit
The unit in which the charge was priced, such as hours, gigabyte-months or requests, matching PricingQuantity. Because providers price the same resource in different units, the unit has to travel with the quantity for a price to be comparable across rows.
Example
A block storage row shows PricingUnit “GB-Mo” with PricingQuantity 500, while the same volume’s usage is recorded in gigabyte-hours.
Where it comes from, per export
The export column that feeds PricingUnit 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 | PricingUnit | as is |
| Azure Cost Management, FOCUS export | PricingUnit | as is |
| Azure Cost Details (actual cost) | Not carried | — |
| Azure Cost Details (amortized cost) | Not carried | — |
| Google Cloud detailed billing export | Not carried | — |
How Runcost uses it
Runcost displays the unit next to every quantity in the drill-down so a reader is never comparing hours to months.
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.