Cost Optimization Guide
Reduce Datadog costs without losing critical signal
Datadog bills on ingestion volume. If every request log is forwarded, costs grow faster than business value.
Why this problem exists
Application defaults emit large volumes of low-signal logs, especially 200 status responses and health checks.
Many teams only configure filtering after costs spike, so ingestion remains high for months.
Real cost and impact
A service producing high request throughput can send terabytes of repetitive logs every month.
Even a 40% noise ratio can represent thousands of dollars in avoidable indexing spend.
Solutions (including alternatives)
- Define explicit keep-rules for errors, anomalies, and security events before defining drop-rules.
- Drop or sample repetitive success logs and route full-fidelity copies to S3 for retention.
- Compare post-ingestion controls with pre-ingestion controls; pre-ingestion usually yields larger savings.
How LogTrim solves it
LogTrim applies filtering and masking before Datadog ingestion, so noisy logs never become billable events.
Teams can route high-signal logs to Datadog while retaining full history in S3.
Example scenario
A team processing 2,500 logs/sec removed repetitive 200 responses and retained only high-signal request summaries.
Net result: 58% lower Datadog ingestion with no loss of incident visibility.
60%
20% is conservative. 80% is common for noisy request and health-check traffic.
Advanced inputs for infra engineers
Throughput-based bill estimate: $3,476 (34,761.43 GB/month)
Current monthly Datadog bill: $9,500
Recoverable noise spend: $5,700
Datadog spend after filtering: $3,800
LogTrim subscription cost: $499
Projected total with LogTrim: $4,299
Net monthly savings after LogTrim cost: $5,201
Net annual savings after LogTrim cost: $62,412
Effective monthly savings rate: 54.75%