FOCUS column
ConsumedQuantity
How much of the resource was actually consumed in the charge period, in the consumed unit: the usage measure independent of how the provider chose to price it. It is the right quantity for unit economics and for anomaly detection, because it moves with behavior rather than with pricing tiers.
Example
A database ran for 24 hours: ConsumedQuantity 24 with ConsumedUnit “Hours”, whatever the pricing unit and tier applied.
Where it comes from, per export
The export column that feeds ConsumedQuantity 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 | ConsumedQuantity | cast to decimal |
| Azure Cost Management, FOCUS export | ConsumedQuantity | cast to decimal |
| Azure Cost Details (actual cost) | Quantity | cast to decimal |
| Azure Cost Details (amortized cost) | Quantity | cast to decimal |
| Google Cloud detailed billing export | usage.amount | cast to decimal |
How Runcost uses it
Runcost builds usage baselines and unit-cost figures on consumed quantity, so a price change and a usage change are told apart.
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.