Skip to main content

Cost Metrics

  • Cost (Billed Cost): The amount you actually pay at the end of the month, after all discounts and credits have been applied.
  • Effective Cost: On AWS, billed cost with upfront Savings Plan and Reserved Instance fees spread across the commitment period. On GCP, a fully offset commitment fee nets to 0 here and on billed cost. A partial fee offset stays on billed cost and is 0 here. Promotional credits stay in. See GCP.
  • List Cost: The cost calculated from public on-demand prices, what you would have paid without any negotiated discounts or commitments. Use this as a benchmark to measure how much you’re saving compared to standard pricing.
  • Contracted Cost: Usage priced before commitment discounts and credits, so the number moves when usage moves. On AWS this keeps the negotiated rate and drops discounts and credits. On GCP every credit amount is dropped, including negotiated discount credits, and Google commitment fees contribute 0. See GCP.
    We advise to track Contracted Cost for your engineering team since it only depends on actual usage. Tracking Billed Cost can be misleading because of Savings Plan reassignments and credits you receive during the year. Learn why Contracted Cost is the right metric for engineering teams

AWS

GCP

Amounts below are USD, after dividing the export amount by currency_conversion_rate. Tax rows (cost_type = tax) are dropped. Each credit in the export becomes its own row, and each metric keeps or zeroes that row on its own.

What Contracted Cost includes on GCP

Contracted Cost is the usage charge before credits. Summed across the month it is:
  • Usage cost for on-demand, spot, and overage rows.
  • cost_at_effective_price_default on flexible CUD usage: consumption_model other than Default, and on a detailed export subscription.instance_id set as well. A standard export has no subscription id, so the non-default consumption model alone is enough. Google’s cost on that row is already the CUD price. cost_at_effective_price_default is the default price for the same usage, and there is often no credit row for the difference. A detailed row with a non-default consumption model and no subscription id keeps cost.
  • The gross cost on legacy committed-use usage (a COMMITTED_USAGE_DISCOUNT or COMMITTED_USAGE_DISCOUNT_DOLLAR_BASE credit on the row). The credit itself is 0.
  • Marketplace purchases that are not a Google-issued commitment.
  • The adjustment amount for cost_type of adjustment, credit, or rounding_error, and for the SKU Contract billing adjustment. Credits attached to that adjustment are still 0.
These rows contribute 0:
  • Every credit, whatever its type: PROMOTION, DISCOUNT, SUSTAINED_USAGE_DISCOUNT, SUBSCRIPTION_BENEFIT, RESELLER_MARGIN, FREE_TIER, COMMITTED_USAGE_DISCOUNT, COMMITTED_USAGE_DISCOUNT_DOLLAR_BASE, FEE_UTILIZATION_OFFSET, and any other type.
  • A Google commitment purchase: a fee row that carries FEE_UTILIZATION_OFFSET, an unused spend commitment (subscription set, consumption model Default or empty, no CUD credit, SKU not Commitment v1:), and a resource commitment whose SKU starts with Commitment v1:.
A negotiated price that is already baked into cost or cost_at_effective_price_default stays in Contracted Cost. A negotiated price that arrives as a DISCOUNT credit does not. Contracted Cost does not amortize commitment fees. The fee row is 0. The offset is 0. Nothing is spread over the commitment term. Unused commitment spend remains on Billed Cost and Effective Cost. That is the gap versus cost plus non-promotional credits (committed use discounts, the fee utilization offset, and negotiated discounts):
  • Those credits are negative, and Contracted Cost adds none of them, so it sits above that sum by the credits you included.
  • On flexible CUD usage, Contracted Cost uses cost_at_effective_price_default where your sum uses cost. The difference is the commitment discount embedded in the price, which has no credit row to add back.
  • A fully offset fee is 0 in both numbers. An unused fee, and a Commitment v1: fee, is in your sum and is 0 in Contracted Cost, which pulls Contracted Cost down.
A gap that stays near a few percent through the month is that mix: credits Contracted Cost ignores, plus the default-price uplift on covered usage, minus unused and v1 fees. It is not an amortized fee inside the metric.

Cost after commitment and contract discounts, before promotional credits

Select Unblended Cost or Amortized Cost (unblended_cost and amortized_cost in Explorer and in the query API). On GCP the converter writes one number to both columns: export cost plus every credit except PROMOTION and RESELLER_MARGIN. Kept, so the discount is already applied: COMMITTED_USAGE_DISCOUNT, COMMITTED_USAGE_DISCOUNT_DOLLAR_BASE, FEE_UTILIZATION_OFFSET (the fee and the offset net), DISCOUNT, SUSTAINED_USAGE_DISCOUNT, SUBSCRIPTION_BENEFIT, and FREE_TIER. Dropped: PROMOTION and RESELLER_MARGIN. There is no credit-type filter. The export’s credits.type is consumed while building these columns and is not a dimension you can filter or configure. cos_charge_category is coarser: CUD credits stay on Usage, the fee offset stays on Purchase, and promotion, discount, sustained use, subscription benefit, and reseller margin rows are Adjustment. Excluding Adjustment removes negotiated discounts along with promotions. The PROMOTION and RESELLER_MARGIN exclusion is fixed. A different set of credit types cannot be configured on a metric.

Azure

For Azure, Contracted Cost is identical to Billed Cost because Azure does not expose a separate contracted or negotiated rate in its billing exports. This means the Contracted Cost advantage (isolating usage changes from discount movements) does not currently apply to Azure.

Datadog

Last modified on November 20, 2026