Datadog cost monitoring

Catch a Datadog cardinality spike before the invoice does

CostMon reads Datadog's own Usage Metering API, the same data behind your Datadog invoice, daily and broken down by product and by committed vs. on-demand spend, so a high-cardinality custom metric or a host-count surge shows up in days instead of reconciling into next month's bill.

Start free See how it works

Datadog Usage Metering API — live today

Datadog bills custom metrics by cardinality, meaning unique combinations of metric name and tag values, so a single metric tagged by customer_id or request_id across a growing user base can multiply into a five- or six-figure billable metric count without anyone adding a new metric name. Infrastructure host billing has its own trap: host count is sampled hourly and billed near the peak, so a brief autoscale spike can set the entire month's host-count charge. Log ingestion and log indexing are also separate meters, so a verbose logging change can move two line items at once. None of this shows up as one obvious number until the invoice reconciles it.

Cost anatomy

What actually drives your Datadog bill

Custom-metric cardinality: A custom metric is billed per unique combination of metric name and tag values, not per metric name. One metric tagged by customer_id across a thousand customers is a thousand-plus billable series, not one.
Histogram and distribution multiplier: Histogram and distribution metric types generate roughly five billable custom metrics per tag combination by default, more with percentile aggregations enabled, which multiplies the cardinality bill fast.
Infrastructure host high-water mark: Host count is sampled hourly across the month and billed near the peak, so a short autoscale spike, even just a few hours, can set the host-count charge for the entire month.
Log ingest vs. indexing: Ingesting logs and indexing or retaining them for search are two separate, separately-priced meters. A verbose logging change can move two line items without touching a single dashboard.
OTel metrics default to custom: OpenTelemetry metrics outside Datadog's built-in semantic-convention mappings are billed as custom metrics by default, the same as anything else outside an official integration.

Why CostMon

Built for Datadog spend, from day one

Product and charge type, broken out daily

CostMon reads Datadog's Usage Metering API daily, split by product and by committed vs. on-demand spend, instead of waiting for one monthly subscription total.

Catch a cardinality or host spike early

A daily view surfaces a custom-metric cardinality jump or a host-count surge while it's a small number, not a month later after it's set the whole month's bill.

One view, next to the rest of your stack

Datadog spend lands in the same normalized daily table as AWS, GCP, and every other connected provider, so finance sees one honest total instead of a separate observability invoice.

Read-only, cost-scoped credentials

CostMon connects with a Datadog API key and application key scoped to read-only usage and cost endpoints only. It never touches your monitors, dashboards, or telemetry data.

Cardinalitycustom metrics bill on unique metric+tag combinations, not metric count
Separate meterslog ingest and log indexing bill independently
Dailysync cadence, not monthly

Getting started

Connect, sync, see — for Datadog

01
Connect a read-only API and application key
Add a Datadog API key and application key scoped to the Usage Metering API's read-only cost endpoints. CostMon never touches your monitors, dashboards, or telemetry data.
02
CostMon syncs and normalizes
Estimated and historical cost data is pulled per sub-org, per product, and per charge type on a schedule, then reconciled into the same normalized model as every other provider you connect.
03
See the line before the invoice does
Open a daily, per-product view of Datadog spend and catch a cardinality spike or a host-count surge weeks before it lands on a bill.

FAQ

Common questions about the Datadog connector

How does CostMon connect to Datadog?

Through a Datadog API key and application key scoped to the Usage Metering API's read-only cost endpoints. CostMon never requests access to your monitors, dashboards, or logs themselves, only cost and usage data.

Does CostMon replace Datadog's own usage dashboard?

No. CostMon reads the same Usage Metering API and normalizes it alongside AWS, GCP, and every other provider you connect, so Datadog spend sits in one daily view instead of its own console.

Can CostMon break Datadog spend down by product?

Yes. Costs sync in with product and committed-vs-on-demand detail intact, so you can see trends by product such as APM, logs, infrastructure, or custom metrics, or grouped into cost buckets by team.

How often does Datadog cost data sync?

CostMon's background scheduler syncs on a regular cadence, using Datadog's estimated-cost endpoint for the current and previous month and historical cost for anything further back, so the dashboard reflects a daily view rather than a monthly statement.

What does the Datadog connector cost?

A flat monthly rate per plan, not a cut of your Datadog spend or the savings CostMon helps you find. Free includes 2 connectors; Professional and Enterprise include unlimited connectors.

Connectors

Cloud, AI, and SaaS: all in one place

AWS, GCP, and Azure for cloud; Anthropic, OpenAI, Amazon Bedrock, Vertex AI / Gemini, and Helicone for AI and LLM spend; Snowflake and Databricks for the data cloud; Datadog, GitHub, and Vercel for the rest of the stack. Add CSV import for any tool without a native connector. That's 14 connectors, all normalized into the same unified view.

Connect a provider. See one number.

Connect your first provider and CostMon normalizes it alongside everything else you run. Your team gets one number everyone can check.

Start free See how to connect a provider