Quantify usage of a component resource

Capture daily aggregate usage of component resources, such as core hours or gigabytes, when Service Providers bill by virtual machines or quantity provisioned. This approach allows FinOps Practitioners to account for scenarios such as analyzing usage across auto-scaled compute services when instantaneous APIs cannot capture historical trends.

← Planning & Estimating

Source: FOCUS MCP snapshot
FOCUS editions: v1.3, v1.4
Queries: 1
Mode: Read-only
Library snapshot (UTC): 2026-10-08

Quantify usage of a component resource v1.3

Not in v1.0 sample

Source: FOCUS use-case SQL
Status: Not in v1.0 sample
Results: Not run
Mode: Read-only
Library snapshot (UTC): 2026-10-08

SkuPriceDetails (with its CoreCount and InstanceSeries properties) is absent from the v1.0 sample, so core counts by instance series cannot be summed.

Review the original SQL below and the required columns before using a newer FOCUS dataset.

Original FOCUS SQL

SELECT
    ServiceProviderName,
    ServiceName,
    PricingUnit,
    RegionName,
    JSON_UNQUOTE(JSON_EXTRACT(SkuPriceDetails, '$.InstanceSeries')) AS InstanceSeries, 
    SUM(CAST(JSON_UNQUOTE(JSON_EXTRACT(SkuPriceDetails, '$.CoreCount')) AS UNSIGNED)) AS TotalCoreCount
FROM focus_data_table
WHERE ChargePeriodStart >= ? and ChargePeriodEnd  < ?
AND JSON_CONTAINS_PATH(SkuPriceDetails, 'all', '$.CoreCount', '$.InstanceSeries')
GROUP BY
    ServiceProviderName,
    ServiceName,
    PricingUnit,
    RegionName,
    InstanceSeries

Columns used

Column names from the source use case.

Read the source on focus.finops.org ↗