Why autoscaling raises your Datadog bill

Answer (2026-10-31): Datadog counts your hosts every hour and, on its standard high-water-mark plan, bills the month on "the maximum count (high-water mark) of the lower 99 percent of usage for those hours", excluding the top 1 percent. So a one-off spike shorter than about 1% of the month (roughly 7 hours of a 720-hour month) is dropped, but a scale-out that repeats (a daily HPA peak, a nightly batch) usually lasts more than 1% of hours and becomes the billed host count for the whole month. At Infrastructure Pro list price ($15/host/month annual, $18 on-demand, checked 2026-10-31), each extra peak host costs the full monthly rate even if it ran a few hours a day. Datadog's documented alternative for autoscaling fleets is the hybrid monthly/hourly plan.

Billing rules quoted from Datadog's own docs (Billing, Pricing, Containers Billing), re-read 2026-10-31. Prices are Datadog list prices from datadoghq.com/pricing/list and datadoghq.com/pricing, read 2026-10-31. Your contract may differ.

“Datadog's per-host pricing model is brutal when you autoscale” · “We're getting far better at auto-scaling (HPA)… causes our DD fees to go up (pay per unique host monitored…)”

Public r/sre threads: 1ow3ltg, 1owwfjy

The rule: hourly host counts, top 1% of hours dropped

• Datadog's words: “Datadog meters the count of hosts and custom metrics hourly. The billable count of hosts is calculated at the end of the month using the maximum count (high-water mark) of the lower 99 percent of usage for those hours. Datadog excludes the top 1 percent to reduce the impact of spikes in usage on your bill.” (Billing docs)
• What that means: sort the month's hourly host counts, drop the top 1% of hours, and the highest remaining hour is the host count you pay for, at the full monthly per-host price. In a 720-hour month, 1% is 7.2 hours. Datadog doesn't say how it rounds.
• Same rule for APM hosts and other host-based products (Database Monitoring, Continuous Profiler, Cloud Network Monitoring) on the high-water-mark plan (Pricing docs).
• Non-reporting hosts don't count: hosts with status INACTIVE drop out, though Datadog says that “could take up to 2 hours”.
• What counts as a host: “any physical or virtual OS instance that you monitor”: a VM, a Kubernetes node, an Azure App Service Plan instance, a Heroku dyno, plus EC2, Google Cloud, Azure or vSphere VMs picked up by integrations (no double-billing when the Agent also runs there).

How a short scale-out sets the month's host count

A single spike shorter than the top 1% of hours is excluded. A scale-out that repeats adds up: 3 hours every weekday is 66 hours, 9.2% of the month, far more than 1%. The peak becomes the billed count for all 720 hours.

Example (example inputs, not data)

Example inputs, made up to show the math: the host curves below are invented. They are not from any customer and are not an average. Month = 720 hours. Prices: Datadog Infrastructure Pro $15/host/month billed annually, $18 on-demand; APM $31/APM host/month annual (list, read 2026-10-31). Billed hosts use Datadog's lower-99% rule; each row gives the same answer whether 1% of hours rounds down (7) or up (8).

Reading the table: the weekday-peak fleet averages 45.5 hosts but is billed for 100, 2.2× its average. At annual list price that is $1,500/mo for infrastructure, against $600 for the steady 40. The one-off 5-hour load test at 200 hosts is dropped, because 5 hours is under 1% of the month.

Containers, Kubernetes and Fargate

• One Agent per node, not per container. Datadog: “It is recommended that containers are monitored with a single containerized Agent per host… If you choose to install the Agent directly in each container, each container is counted as a host from a billing perspective.” (Billing docs)
• Container allotment scales with hosts. “Depending on your plan, you can monitor 5 or 10 containers free for each host license. The container count is averaged across your entire infrastructure.” For autoscaling groups, Datadog says “the total container allotment also increases” during peak hours, because the allotment follows the host count (Containers Billing docs).
• Over the allotment: $0.002 per container per hour on-demand, or prepaid at $1 per container per month (datadoghq.com/pricing). Containers are metered every 5 minutes and averaged per hour, so “1200 on-demand containers during a single five-minute interval” are metered as 100 container hours. Pause containers and the Agent's own containers don't count.
• AWS Fargate is not a host. “Fargate is charged based on the concurrent number of monitored tasks in ECS Fargate and the concurrent number of monitored pods for EKS Fargate.” The AWS Fargate tab on datadoghq.com/pricing lists Serverless Application Monitoring from $3 per active application instance per month (annual; $4.32 on-demand) and Serverless Application APM from $6 ($9 on-demand), averaged over 5-minute intervals.
• GKE Autopilot is billed under the Serverless category, unlike GKE Standard.

Example (example inputs, not data): 40 Kubernetes nodes running 260 containers all month on Infrastructure Pro. With one Agent per node: 40 hosts × $15 = $600, plus 60 containers over the 200 included × 720 h × $0.002 = $86.40 on-demand (or 60 × $1 = $60 prepaid). With the Agent inside every container, Datadog counts each container as a host: 260 × $15 = $3,900.

Levers Datadog documents

1. Ask about the hybrid monthly/hourly plan (MHP). “You commit to a monthly minimum, and any host hours above that commitment are billed at an hourly rate… well-suited to ephemeral environments, such as autoscaling fleets or short-lived workloads.” The high-water-mark plan is “well-suited to environments with stable usage throughout the month.” The hourly rate isn't on the public list (Pricing docs).
2. Commit to the baseline, not the peak. Infrastructure Pro is $15 annual vs $18 on-demand; APM $31 vs $36. Plan & Usage → Subscription Details shows your contract and on-demand price per product.
3. Run one containerized Agent per node (a DaemonSet in Kubernetes), never one per container.
4. Prepay containers you always run. $1 per container per month prepaid vs $0.002 per container hour on-demand. Use Container Discovery Management to limit which containers are monitored.
5. Stop the AWS integration from billing hosts you don't need. Under “Limit Metric Collection to Specific Resources” you can filter EC2 by tag (for example !datadog:no). Hosts with a running Agent are still billed (AWS Integration Billing docs).
6. Check how bursty jobs on Fargate would bill. Datadog bills Fargate on concurrent monitored tasks or pods, not on the host high-water mark. Price both before moving anything.

How to explain the bill to leadership

Buyers describe the moment: “leadership asked why observability costs so much”, and one fix: “showing our CTO a graph of host count vs Datadog bill” (r/sre).

1. Show the graph: hourly host count for the month, with two lines: the average and the billed count (the high-water mark of the lower 99%). Like the chart above.
2. Name the rule in one sentence: “On the high-water-mark plan, Datadog bills our infrastructure and APM hosts on the highest host count we hold for more than about 1% of the month’s hours.”
3. Price the gap: (billed hosts − average hosts) × your per-host rate for Infra + APM. That is the cost of the peak.
4. Give two options with owners: the hybrid monthly/hourly plan (ask your Datadog rep for the hourly rate), and engineering changes (one Agent per node, Fargate for bursty jobs, integration filters).
5. Show the whole stack: Datadog plus anything else you pay for, next to your cloud bill. The audit report is built to hand over.

How other vendors bill the same peak

Billing-unit contrast, not a quote or a like-for-like feature comparison. Rates from our dataset (vendor pages read 2026-10-31), applied to the same made-up weekday-peak curve (32,760 host-hours in the month).

Hourly billing charges the peak only for the hours it runs. These products differ in features, retention and included data, so price them on your full usage before deciding.

FAQ

Related

• Cut your Datadog bill without migrating
• How to cut your Datadog bill
• Datadog cost calculator
• Datadog pricing (2026)
• Datadog alternatives (cheaper)
• Datadog vendor page
• All guides

Data: Datadog autoscaling and host billing, Datadog docs and list prices read 2026-10-31. Source: O11y Watch (https://o11y-watch.pages.dev). License: CC BY 4.0. Please attribute "O11y Watch" with a link to https://o11y-watch.pages.dev/.