# Datadog Container Usage Exceeding Per-Host Allotment Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/datadog-container-usage-exceeding-per-host-allotment Each Datadog Infrastructure host license on the Pro or Enterprise plan includes a small number of monitored containers, 5 or 10 per host depending on... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Each Datadog Infrastructure host license on the Pro or Enterprise plan includes a small number of monitored containers, 5 or 10 per host depending on the plan, pooled across the whole account. PointFive Research Cloud cost research at PointFive Datadog service [Datadog Infrastructure Monitoring](https://www.pointfive.co/efficiency-hub/cloud-services/datadog-infrastructure-monitoring) Category [Other](https://www.pointfive.co/efficiency-hub/service-category/other) Reference CER-0544 Type Excessive Ingestion or Processing ## Explanation Why the waste happens and who it affects. Dense Kubernetes nodes, sidecar-heavy pods, short-lived job containers and crash-looping pods can push the average container count above that allotment, and every container above it is billed per container-hour at the on-demand rate. Datadog meters containers in five-minute increments, so even short bursts of many containers add billable container-hours. The waste has two forms: monitoring containers nobody needs data from, such as sidecars, init-style utility containers or whole non-production namespaces, and paying on-demand rates for a steady container baseline that could be covered by prepaid containers. It grows on Agent-monitored Kubernetes and ECS clusters as sidecars and microservices are added while the host count, and therefore the allotment, stays flat. ## Billing model The pricing dimensions that drive this cost. Container usage is compared each hour against an allotment made of included containers plus any contracted container commitment. Included containers 5 containers per host on Pro and 10 per host on Enterprise, averaged across all infrastructure On-demand containers Containers above the allotment, billed per container per hour ($0.002 per container-hour on the public pricing page) Prepaid containers A contracted container commitment billed per container per month ($1 on the public pricing page) that raises the allotment Five-minute metering Container counts are sampled every five minutes, averaged over each hour, and the allotment is deducted hour by hour ## How to detect 4 checks to find it in your estate. - Chart datadog.estimated\_usage.containers and datadog.estimated\_usage.containers.by\_tag against the allotment (hosts times 5 or 10, plus any prepaid containers) to see when and where usage goes over - In Plan and Usage, use the Billable view of Usage Details to see how many container-hours are billed on demand each month - Break container usage down by kube\_namespace, image and container name to find sidecars, utility containers and non-production namespaces that add many containers but are not used in dashboards or monitors - Look for pods in CrashLoopBackOff and high-churn Jobs or CronJobs: any container that runs for more than ten seconds counts in that metering interval ## How to fix 5 ways to remove the waste. - Exclude containers that do not need monitoring with Container Discovery Management, for example DD\_CONTAINER\_EXCLUDE by image, name or kube\_namespace (Agent 7.20+), or the ad.datadoghq.com/exclude pod annotation; excluded containers send no metrics or logs - Keep the default pause container exclusion enabled (DD\_EXCLUDE\_PAUSE\_CONTAINER), which stops pause containers from counting as billable - If a steady container count above the allotment remains, buy prepaid containers for that baseline through your account team instead of paying on-demand container-hours - Fix crash-looping workloads and consolidate low-value sidecars; each removed container reduces billable container-hours on every node where it runs - Tradeoff: excluded containers disappear from Datadog metrics and logs, so confirm no monitor, SLO or dashboard depends on them; kubernetes.containers.running and docker.containers.running still count all containers ## Documentation Vendor references for pricing and configuration. - [Containers Billing docs.datadoghq.com](https://docs.datadoghq.com/account_management/billing/containers/) - [Container Discovery Management docs.datadoghq.com](https://docs.datadoghq.com/containers/guide/container-discovery-management/) - [Datadog Pricing List datadoghq.com](https://www.datadoghq.com/pricing/list/) - [Estimated Usage Metrics docs.datadoghq.com](https://docs.datadoghq.com/account_management/billing/usage_metrics/) - [Usage Details docs.datadoghq.com](https://docs.datadoghq.com/account_management/plan_and_usage/usage_details/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Datadog Infrastructure Monitoring CER-0543 ### [Unfiltered Datadog Cloud Integrations Billing Non-Essential Hosts](https://www.pointfive.co/efficiency-hub/inefficiencies/unfiltered-datadog-cloud-integrations-billing-non-essential-hosts) Datadog's AWS, Azure and Google Cloud integrations discover virtual machines by crawling the cloud provider's APIs, and every VM they pick up becomes a billable Datadog host, whether or not the Datadog Agent is installed on it. When an... Other - Datadog Log Management CER-0539 ### [Indexing All Ingested Datadog Logs Without Exclusion Filters](https://www.pointfive.co/efficiency-hub/inefficiencies/indexing-all-ingested-datadog-logs-without-exclusion-filters) Datadog Log Management charges separately for ingesting logs and for indexing them. At list prices, indexing a million 1 KB events for 15 days ($1.70) costs many times more than ingesting that gigabyte ($0.10). By default a log index has... Other - Datadog Custom Metrics CER-0540 ### [High-Cardinality Tags Inflating Datadog Custom Metrics](https://www.pointfive.co/efficiency-hub/inefficiencies/high-cardinality-tags-inflating-datadog-custom-metrics) Under Datadog's cardinality-based pricing, a custom metric is a unique combination of a metric name and tag values, including the host tag. Every new tag value creates a new billable timeseries, so a metric tagged with an unbounded... Other --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.