r/aws
Datadog costs that quietly outpace your actual AWS growth - the mechanics
- upvotes
- 10
- comments
- 4
Post
Highlighted: the lines this signal was extracted from
Been seeing "why is our Datadog line item bigger than half our AWS bill" come up enough that it's worth writing down the actual mechanics, since none of them are Datadog doing anything wrong, they're just invisible until the invoice. Custom metric cardinality. You're billed per unique tag-value combination, not per metric. A metric tagged with customer_id looks cheap at 50 customers. Add one more tag with 40 distinct values and you're not adding cost, you're multiplying it, 50 time series becomes 2,000 on something that "didn't change." Log indexing separate from ingestion. Ingestion is cheap, indexing isn't, and the default is to index everything unless someone's scoped it down with exclusion filters. A logging level left at debug in one Lambda or ECS service can 10x indexed volume overnight with zero AWS-side change. APM span indexing. Same shape as logs. A sampling rate change, or just a new high-traffic route joining an existing trace, moves you from a small sampled fraction toward near-full indexing. Host-tier pricing steps. Per-host pricing has boundaries, not a smooth curve. An ASG scaling event during a traffic spike can cross a tier line and produce a jump that's out of proportion to what actually changed in EC2. The pattern that trips people up: your AWS bill moves with real usage, your Datadog bill moves with telemetry configuration, and almost nobody treats...
Keep reading with a free account
The rest of this post, and every signal for Datadog, is in your free account.
Also quoted as evidence
The pattern that trips people up: your AWS bill moves with real usage, your Datadog bill moves with telemetry configuration, and almost nobody treats telemetry config with the same scrutiny as infra.
From the post