Datadog Log Management
Datadog Log Management covers collection, pipelines, indexing, search, archives, forwarding, and rehydration.
Read the page as a transparent path: establish context, inspect the evidence, then test the published stance.
Catalog position
Log Management is modeled independently from Datadog's other signals because its pipeline, retention, archive, and pricing boundaries are log-specific [1].
Evidence boundary
The profile does not equate ingestion with indexing or assume archive and rehydration are included in the same cost meter [1].
Source record
Bibliography
Datadog, ‘Log Management documentation.’ [Online]. Available: https://docs.datadoghq.com/logs/. [Accessed: Aug. 17, 2026].
Documents log collection processing indexing search archives and rehydration.Canonical source ↗Return to article ↑Datadog, “Datadog pricing list.” [Online]. Available: https://www.datadoghq.com/pricing/list/. [Accessed: Aug. 14, 2026].
Official price-list or product-site reference. Availability: published.Canonical source ↗Return to article ↑Datadog, “Datadog Agent repository.” GitHub. [Online]. Available: https://github.com/DataDog/datadog-agent. [Accessed: Aug. 14, 2026].
Known limits
Unresolved unknowns
- Ingestion indexing retention archive rehydration and scanning can have separate meters.
Public review
Discuss and correct
Comments are public. Proposed factual corrections must be incorporated into version-controlled research before they are treated as published.
Local preview does not have Giscus configured. Native comments and Giscus are never presented as competing primary systems on the same page.