Use Case
Drop repetitive 200 logs
Suppress high-volume success noise before Datadog ingestion.
Problem
HTTP 200 request logs can dominate volume in production APIs and drown meaningful signals.
Teams often pay to ingest millions of success events they never investigate.
Example
A service logs every successful health check, static asset request, and cache hit.
Monthly ingestion grows while incident response still depends mostly on 4xx, 5xx, and latency anomalies.
Solution (LogTrim)
Define keep rules for error and anomaly paths first.
Drop repetitive 200 classes and route full-fidelity copies to S3 for retention safety.
Continuously review drop impact against alerts and post-incident needs.
Continue to full guide
Review the complete implementation guide and rollout strategy for this use case.