Cost Optimization Guide
Route logs to Datadog and S3 with a signal-first strategy
Datadog is ideal for high-signal operational workflows. S3 is better for low-cost bulk retention.
Why this problem exists
Teams often keep all logs in one expensive system because routing strategy was never formalized.
Retention needs and real-time troubleshooting needs are different workloads.
Real cost and impact
Keeping full fidelity in premium indexed storage is one of the biggest observability cost multipliers.
Separating hot and cold log paths can materially lower monthly spend.
Solutions (including alternatives)
- Route alerts, security signals, and error paths to Datadog.
- Route full raw streams to S3 for long-term retention and audits.
- Review keep/drop policies quarterly as traffic and product features evolve.
How LogTrim solves it
LogTrim routes high-signal events to Datadog and archives full streams to S3 in real time.
This provides operational speed and retention coverage without paying Datadog rates for every event.
Example scenario
A marketplace backend kept incident-critical events in Datadog while storing all raw access logs in S3.
The team retained complete history with lower indexed volume.