LogTrim

Slash your Datadog costs

No migrations, No retooling, No compromises, Massive savings.

Calculate my savings
Savings

Cut noise before it gets expensive

Modeled savings
$7,320/mo

73.2 TB trimmed at $0.10/GB.

Trim rate
47.2%

Noise removed before Datadog.

ROI
732.7%

Monthly return after LogTrim.

How it works

Archive raw. Forward signal.

LogTrim pipeline flowRaw logs enter LogTrim, raw logs archive to S3, and a smaller clean stream reaches Datadog as logs and metrics.LOGSLOGTRIMTRIMMASK PIIDEDUPESAMPLELOG TO METRICS3 BUCKETRaw logsLOGSMETRICSDATADOG
Core Features
Six controls for reducing Datadog costs
Filter

Drop low-value events upstream so they never become billable Datadog ingestion volume.

Archive

Send raw logs to cheaper long-term storage while forwarding only high-signal data to Datadog.

Log-to-Metric

Turn high-volume success patterns into request counts, rates, and latency metrics instead of raw indexed logs.

Sample

Keep representative logs for noisy success traffic while preserving complete errors, warnings, and anomalies.

Deduplicate

Collapse repeated events into one representative log with a count, first-seen time, and last-seen time.

Mask PII

Redact emails, IP addresses, phone numbers, and sensitive tokens before logs reach indexed storage.

Log out
Dashboard

LogTrim

Scale plan

DayWeekMonth
Estimated SavingsEdit

$7,320.00/month

Calculated from volume saved over the last 30 days at $0.10/GB Datadog ingest pricing.

  • Saved volume over last 30 days: 73200.00 GB
  • Average daily savings: $244.00
  • Projected monthly savings: $7,320.00
  • ROI: 732.7% monthly return
Egress Failures

0

Batches that exhausted retry policy over the last 30 days.

Logs Received

206.8B

Total logs recorded in the last 30 days.

Logs Trimmed

47.2%

Trimmed logs versus received logs in the last 30 days.

Pipeline Config

Active policy

11/17 policy controls are enabled.

Summary
Enabled
11
Disabled
6
Destinations
DatadogS3
Activity SummaryLast 30 days

47.2% trimmed

Operational totals and destination routing.

Received logs206,800,000,000
Trimmed logs97,609,600,000
Forwarded logs109,190,400,000
Saved volume73200.00 GB
Recent failures

Dispatch health

No permanent failures recorded.
Trim Intelligence

Top active trim rules

Rule-level trim counts for the selected range with config-derived sample patterns.

  • 1. Trim health and synthetic probes
  • 2. Trim HTTP 200s
  • 3. Enable PII masking
Log out
Pipeline

Pipeline Settings

Configure how your logs are processed and where they're sent.

Preview mode

Destinations

Datadog

Primary Datadog egress for trimmed logs.

‹

S3

Archive copies for long-term storage.

‹

Rules

Safe noise reduction

High-volume logs that usually add cost without adding incident signal.

✓

Trim HTTP 100s

Trim 1xx informational request logs before routing.

ExamplesAdvanced‹
✓

Trim HTTP 200s

Trim 2xx request logs before they hit paid retention.

ExamplesAdvanced‹
✓

Trim HTTP 300s

Trim 3xx redirect request logs before routing.

ExamplesAdvanced‹
Save pipeline config
Log out
Organization

LogTrim

Manage organization membership, roles, and invite-code access.

Join code

Owners and admins can generate a short-lived code for a new user to join this organization.

Generate join codeCodes expire after 7 days.

Active join codes

LT-7Q4K

Created Apr 22, 2026. Expires Apr 29, 2026.

Invalidate

Members

3 members

Owners can transfer ownership and change roles. Admins can add or remove non-owner members. Members can only leave.

maya@logtrim.devYouOwner

Joined Apr 12, 2026

Leave
ops@logtrim.devAdmin

Joined Apr 18, 2026

DemoteRemove
dev@logtrim.devMember

Joined May 2, 2026

PromoteMake ownerRemove
How LogTrim compares
Why teams choose LogTrim
Datadog native filtering
Where It Fits

Strong for parsing and enrichment of logs you already keep inside Datadog.

Because it runs after ingestion, it is weaker for teams trying to cut ingestion-driven spend.

LogTrim filters and masks before ingestion, then forwards only high-signal events to Datadog.

Vector
Where It Fits

Powerful general-purpose pipeline when your team wants deep low-level composition.

For most teams, it means about two days of setup, then permanent ownership, plus a "who maintains this when Dave leaves" risk.

LogTrim is purpose-built for teams who would rather not own another piece of infrastructure.

Cribl
Where It Fits

A strong option for organizations running broad observability programs with dedicated platform ownership.

In practice, many teams face a $15K professional services engagement before they see value.

LogTrim stays narrow: suppress noise, mask PII, and route signal to Datadog plus full retention in S3.

Starter
$299/month
For teams starting to control Datadog log spend.
Limit
Up to 2 TB/day
Includes
Filtering, masking, deduplication, sampling, metrics, Datadog, and S3
Capacity
Shared
Start with Starter
Growth
$599/month
For teams with sustained multi-service log volume.
Limit
Up to 5 TB/day
Includes
Filtering, masking, deduplication, sampling, metrics, Datadog, and S3
Capacity
Shared
Start with Growth
Scale
$999/month
For high-volume teams not yet ready for Enterprise.
Limit
Up to 10 TB/day
Includes
Filtering, masking, deduplication, sampling, metrics, Datadog, and S3
Capacity
Shared
Start with Scale
Enterprise
Custom
For 10 TB+/day workloads that need dedicated infrastructure.
Limit
10 TB+/day negotiated capacity
Includes
Dedicated capacity, SAML SSO, audit logs, and SLA
Capacity
Dedicated regional
FAQ
Frequently asked questions

Why is Datadog so expensive?

Datadog log billing is mostly ingestion-driven. If you forward every event, low-value traffic like repetitive 200 responses increases costs quickly.

Can I drop logs before Datadog?

Yes. LogTrim applies filtering rules before ingestion so you only send high-signal logs to Datadog.

What logs are safe to drop?

Most teams safely drop repetitive success logs, health checks, and known noise once they confirm those events are not used in alerts or incident workflows.

How much can I save?

Savings depend on your noise ratio. Teams that remove low-signal traffic commonly reduce Datadog ingestion spend by 30-60%. LogTrim has even seen teams reduce their Datadog bill by more than 70%.

Is log filtering safe?

Filtering is safe when rules are explicit, tested, and paired with low-cost archival. LogTrim supports dual routing so full logs can still be retained in S3.

Can I convert logs into metrics before Datadog?

Yes. LogTrim can derive metric signals from log streams so you keep high-value trends without indexing every raw event.

Does LogTrim support sampling and deduplication?

Yes. You can sample repetitive traffic intentionally and suppress duplicate events before they become Datadog ingest cost.

Which log source formats does LogTrim support?

LogTrim accepts Datadog-compatible JSON, OTLP JSON logs, Fluentd-style JSON, and LogTrim native JSON. Pick the endpoint that requires the smallest change to your current shipper.

Which endpoint should I send logs to?

Use /api/v2/logs for Datadog-compatible clients, /v1/logs for OTLP JSON, /fluentd for Fluentd-style payloads, or /ingest for direct application posts using the LogTrim native JSON envelope.

What does the LogTrim native JSON envelope look like?

The native envelope is a JSON object with a top-level logs array. Each log includes level, message, and service, with optional fields such as host, path, timestamp, status_code, and any extra attributes: {"logs":[{"level":"ERROR","message":"checkout failed","service":"api","status_code":500}]}.

What authentication header is required for ingest?

Every ingest endpoint currently requires a dd-api-key header containing the Datadog API key saved in pipeline settings.

Read all FAQ answers
Cut the bill
See the savings before you change the pipeline.
Calculate my savings
Resources
Case studiesReduce Datadog costsFilter logs before DatadogDatadog cost calculatorLogTrim vs Datadog pipelines