Explanation
Why the waste happens and who it affects.
Commitments are set at contract signing, while usage keeps changing: host counts grow, teams adopt new products such as Flex Logs, RUM or Database Monitoring mid-term with no commitment line, or log and span volumes climb past the committed quantity. Every unit above the commitment is then billed at the on-demand rate for the rest of the term.
On Datadog's public pricing page, 15-day Standard Indexing for logs is $1.70 per million events billed annually versus $2.55 on demand, and the pricing page's log FAQ says volume above a commitment is billed at +50% of the annual price. The waste falls on whoever owns the Datadog contract, typically FinOps or procurement, and is hard to see from engineering dashboards because usage looks normal and only the rate changes.
Billing model
The pricing dimensions that drive this cost.
Each committed product carries a contract price and an on-demand price, both shown in Plan and Usage.
- Committed usage
- Volume purchased in the contract and billed at the contract price, typically the annual rate on the pricing page
- On-demand usage
- Billable usage above the committed and allotted quantities, charged at the higher on-demand price
- High watermark plan (HWMP)
- Hosts billed on the maximum of the lower 99 percent of hourly counts for the month
- Hybrid monthly/hourly plan (MHP)
- A monthly minimum commitment is charged, and host hours above it are billed at an hourly rate
How to detect
5 checks to find it in your estate.
- In Plan and Usage, switch Usage Details to the Billable view and turn on See included usage: purple on-demand pills show the share of each product billed on demand, and the dashed Committed line shows the commitment per product
- Compare quantity, contract price and on-demand price for each committed product in the Subscription Details section of the Billing page
- Check Cost Summary for projected end-of-month costs by product, and review the last several months to find products that are billed on demand every month rather than only during spikes
- Enable first-time usage notifications to be emailed when a product not included in the current contract starts generating billable usage
- Build monitors on datadog.estimated_usage.* metrics (for example datadog.estimated_usage.logs.ingested_bytes or datadog.estimated_usage.apm.ingested_bytes) with thresholds set at the committed monthly quantity
How to fix
4 ways to remove the waste.
- Size commitments at renewal, or through a contract amendment with your account team, to the steady baseline shown in the Billable view, and add commitment lines for products adopted mid-term that bill on demand every month
- Choose the host billing plan that fits the fleet: HWMP for stable host counts, MHP for autoscaling or short-lived hosts where the hourly rate above the minimum is cheaper than a high watermark
- Reduce the usage driving the overage where it is not needed, for example with log exclusion filters, APM sampling and retention filters, or container and host filters on cloud integrations
- Tradeoff: committing above real usage replaces on-demand overage with paid-for volume that is not used, since committed amounts (such as the MHP monthly minimum) are charged regardless, so base commitments on sustained usage rather than peaks
Documentation
Vendor references for pricing and configuration.