LogHouse Editorial · Published 2026-08-12 · Updated 2026-09-04 · 8 min read
Datadog Log Management Pricing Explained
How Datadog log billing typically works—ingest, indexing, retention, Flex Logs, and archives—without treating list prices as quotes.
The short answer
Datadog log cost is usually a combination of how many gigabytes you send, how many events you index or keep queryable, and how long you retain them. Flex Logs and archives change the mix, but they do not remove the need to decide which logs deserve premium treatment. Always confirm current rates on Datadog’s pricing pages; this article explains the model, not a quote.
The three meters most teams hit
Ingest is the volume that arrives. Indexing (or equivalent query-ready storage) is the subset you want to search quickly. Retention is how long that subset stays online.
A chatty service can be cheap to generate and expensive to keep searchable. That is why “we only log errors” conversations start after the first large invoice, not before.
Flex Logs and archives
Datadog Flex Logs and archive products exist because not every event should live in standard indexed storage. They can lower unit cost for older or lower-priority data, with trade-offs around query speed, rehydration, or which features apply.
They are still Datadog products, billed on Datadog terms. If the goal is months of immediately searchable application logs at analytical-storage economics, a dedicated log backend is a different design.
How to read your invoice
Look at which services dominate ingested GB, which indexes stay enabled, and which retention settings were left at defaults. Exclusion filters and sampling help, but they also hide the evidence you later need.
Use your own spend in a calculator rather than published round numbers. Vendor list prices change, committed discounts vary, and on-demand overage is where surprise lives.