Indexing exclusion filters
Toilsome setup and ongoing maintenance.
Bills 100% of ingestion even for excluded logs.
Bills 100% of ingestion even for excluded logs.
Automatically reduces noise before Datadog sees it.
Datadog + Grepr
Optimize Datadog.
Cut your bill by 90%.
Grepr is the Autonomous Telemetry Pipeline that automatically reduces 90% of your Datadog noise without migrations or disruption to Datadog dashboards and alerts.
Datadog isn’t the problem. It’s the expensive, noisy telemetry you don’t use.
It is a telemetry-volume problem. Engineering teams ship more services, more background jobs, and more debug events. And AI-assisted development accelerates the pace in a way that’s unsustainable. Your Datadog bill compounds as your telemetry data grows.
The usual Datadog cost fixes and why they fall short
Indexing exclusion filters
Flex Logs / Log Archives
Flex Logs / Log Archives
Rehydration is painfully slow, and you pay extra on top of ingestion.
Raw telemetry goes to low-cost storage and can be backfilled into Datadog on-demand.
Datadog Observability Pipelines
Datadog Observability Pipelines
Requires building toilsome routing rules.
Automatically reduces noise before it's billed in Datadog.
Trace sampling rules for APM
Trace sampling rules for APM
Requires ongoing tuning, and most traces are dropped before you know if they're interesting.
Identifies anomalous traces dynamically rather than sampling at a fixed rate.
Custom metrics cardinality limits
Custom metrics cardinality limits
Requires anticipating dimensions to drop in advance, creating blind spots during an incident.
Preserves interesting metric dimensions needed during an incident.
Indexing exclusion filters
Requires someone to manually identify noisy log patterns, write exclusion queries per index, and revisit them as services and log formats change. Still bills 100% of ingestion even for excluded logs.
Grepr's signal processing engine continuously detects and reduces noise upstream, before Datadog ever sees it, so there's nothing to write or maintain.
Flex Logs / Log Archives
Moves logs to cheaper storage, and lets you rehydrate when needed. But rehydration is slow (often takes hours), and you're still paying Datadog's archive and rehydration pricing on top of ingestion.
Raw telemetry lands in your own low-cost data lake from the start, and Grepr can backfill detail into Datadog on-demand without a rehydration workflow.
Datadog Observability Pipelines
Datadog's own pipeline product requires you to configure processors and routing rules. And it's built to keep your data inside Datadog's ecosystem rather than reduce what you pay Datadog.
Grepr sits upstream of Datadog, automatically reduces volume before it's billed anywhere, and isn't tied to keeping you on any given platform.
Trace sampling rules for APM
Static head-based sampling rates mean most traces are dropped before anyone knows whether they're interesting. And tuning sample rates per service is ongoing, manual work.
Grepr's stateful engine can identify and retain anomalous or rare traces dynamically, rather than sampling at a fixed rate, regardless of what's happening.
Custom metrics cardinality limits
Capping cardinality to control costs means picking which dimensions to drop in advance, often blinding you to exactly the high-cardinality slice that matters during an incident.
Grepr reduces metric volume based on actual usage patterns rather than preset caps, preserving the dimensions that turn out to matter.
Grepr gives you a better option
Reduce expensive, noisy telemetry before it’s ingested into Datadog, and preserve raw telemetry in low-cost storage for those rare moments you need it.
How to optimize Datadog with Grepr
Keeps using Datadog as you always have. Your Dashboards, alerts, runbooks, and investigations stay connected to the same workflows.
Area
Without
With
Telemetry ingestion volume
Full — all telemetry sent to Datadog.
Only high-value signal is sent is to Datadog; low-value noise goes to a low-cost data lake.
Telemetry ingestion cost
Scales with telemetry growth (unsustainable).
Up to 90% noise reduction results in up to 75% observability TCO reduction.
Raw data access
Limited to what Datadog retains.
Preserved in low-cost storage for search and automatic backfill during incidents.
Dashboards and alerts
Unaffected.
Unaffected: Grepr's query translation engine reads your existing dashboards and alerts and automatically ensures the data they depend on is routed through.
Developer toil
Increased: Developers required to set up filtering to control costs.
Reduced: No tinkering required–Grepr automatically eliminates noise.
SRE toil
Increased: Manual log tuning, retention debates, filter maintenance, and slogging through noise.
Reduced: Autonomous signal processing engine eliminates noise.
Deployment effort
N/A
30 minutes: Single configuration change. No migration required.
Grepr sits between your telemetry sources and Datadog.
Point your log shippers and agents to Grepr with a single configuration change.
Our signal processing engine automatically eliminates noise. Every two minutes, Grepr sends a summary, such as the qty of repeated patterns with summary statistics.
For example, sending patterns such as request failed for user <*> while preserving configured fields and exceptions.
For example, sending patterns such as request failed for user <*> while preserving configured fields and exceptions.
Raw telemetry remains available in a low-cost data lake. Grepr preserves IDs, IPs, status codes, URL paths, attributes, services, and environments where configured.
Grepr's query translation engine reads your existing dashboards and alerts and automatically ensures the data they depend on is routed through.
Grepr can manually or automatically backfill data based on triggers such as incidents, anomalies, support tickets, or investigations.
Grepr’s processing jobs can run in batch or stream, allowing teams to test processing logic on a file or existing data before turning it into a live workflow.
Connect with one-line config
Point your log shippers and agents to Grepr with a single configuration change.
Eliminate noise
Grepr’s signal processing engine automatically eliminates telemetry noise before it reaches your observability platform. Every two minutes (configurable), Grepr aggregates the repetition and emits a summary as a single log, such as how many times the pattern repeated along with summary statistics.
For example, related messages can be generalized into a pattern such as request failed for user <*> while preserving configured fields and exceptions.
Preserve low-value noise for investigations at a fraction of Datadog’s cost
Raw telemetry remains available in a low-cost data lake. Grepr preserves IDs, IPs, status codes, URL paths, attributes, services, and environments where configured.
Protect dashboards and alerts
Grepr's query translation engine reads your existing dashboards and alerts and automatically ensures the data they depend on is routed through.
.png)
Backfill archived noise when needed
Grepr can manually or automatically backfill data based on triggers such as incidents, anomalies, support tickets, or investigations.
.png)
Test before streaming live
Grepr’s processing jobs can run in batch or stream, allowing teams to test processing logic on a file or existing data before turning it into a live workflow.
Lower bills. Same visibility. No compromise.
Keep using Datadog. No migrations.
Grepr is not a Datadog alternative. Keep using Datadog exactly as you always have.
Eliminate low-value noise.
Grepr’s signal processing engine automatically reduces telemetry noise before it reaches Datadog.
Focus on your products, not observability tooling.
Grepr detects millions of patterns, signatures, and trends dynamically. No toilsome rule-building. No log audits. No routing rules to update each sprint. No policing log volumes.
Cost controls that scale with you.
As you ship more software and produce more telemetry, Grepr scales with you, automatically identifying noisy telemetry in real time.
Datadog federated search
Use Datadog's federated log search to query data from Grepr's data lake without switching tools.
Reducing telemetry volume only helps if you can still get to the data the moment you need it. Datadog’s Log Explorer lets you query data stored in Amazon S3 directly from the Datadog UI.
No separate dashboard, no new query language, no retraining your team.
The Grepr UI is still there for building pipelines and managing your signal processing logic. But for day-to-day investigation, your team never has to leave Datadog.
Reduce Datadog noise by 90%
"Grepr helped us automate what to keep and what to skip, so we’re not paying to store or index noise. It lets us find the needle in the haystack without paying for the haystack!"
Evan Robinson, CTO atJitsu
How Jitsu Cut Logging Costs by 90% While Managing Millions of Shipments Generating 400 Logs Each
"Since we deployed Grepr, we’re seeing a 95% reduction in log volume and didn’t have to change a thing in our app. I'd recommend Grepr to any team that's experiencing rising costs from an expensive logging platform!"
.png)
Dave Bortz, VP Engineering at FOSSA
Case Study: How FOSSA Reduced Their Logs by 95% Without Burdening Their Engineers
“Engineers didn't change how they work at all. Dashboards and alerts still worked as expected. We just stopped paying for 90% of our log volume that was never doing anything for us.”
Ben Ede, Director of Engineering at Envoy
9 Days from Kickoff to Production: How Envoy Cut Log Volume by 90%
“After seeing what Grepr did to reduce our logs noise, extending it to traces was an easy call. We were seeing the same pattern: a lot of volume, most of it not particularly useful, and a Datadog billing model that scaled with every new host we spun up.”
Dave Bortz, VP Engineering at FOSSA
How Envoy Cut Log Volume by 90%
"Grepr helped us automate what to keep and what to skip, so we’re not paying to store or index noise. It lets us find the needle in the haystack without paying for the haystack!"
Evan Robinson, CTO atJitsu
Learn More
"Since we deployed Grepr, we’re seeing a 95% reduction in log volume and didn’t have to change a thing in our app. I'd recommend Grepr to any team that's experiencing rising costs from an expensive logging platform!"
Dave Bortz, VP Engineering at FOSSA
Learn More
“Engineers didn't change how they work at all. Dashboards and alerts still worked as expected. We just stopped paying for 90% of our log volume that was never doing anything for us.”
Ben Ede, Director of Engineering at Envoy
Learn More
“After seeing what Grepr did to reduce our logs noise, extending it to traces was an easy call. We were seeing the same pattern: a lot of volume, most of it not particularly useful, and a Datadog billing model that scaled with every new host we spun up.”
Dave Bortz, VP Engineering at FOSSA
Learn More
FAQs
By how much can I reduce my Datadog costs with Grepr?
Typically up to 90%, but it depends on how noisy your telemetry is. Teams running chatty services, health checks, retry loops, debug logs, and repeated lifecycle events tend to have more reducible volume. Jitsu reduced Datadog log costs by 90% with Grepr. Book a demo for an estimate based on your actual environment.
Do I need to replace Datadog?
No. Grepr is vendor-neutral and works with Datadog. High-value signal is automatically forwarded to Datadog (or, Splunk, New Relic, Grafana Cloud, OpenTelemetry, and common log forwarders).
Do I need to modify my Datadog configuration?
A single configuration change points your Datadog agents to Grepr. No agents to install, no re-instrumentation, and no migrations.
What happens to telemetry datal that Grepr decides is “noisy”?
Grepr preserves raw data in low-cost storage for backfill and incident investigation.
Will dashboards and alerts still work?
Grepr's query translation engine reads your existing dashboards and alerts and automatically ensures the data they depend on is routed through.
Will Grepr sample my telemetry data?
No. Sampling usually selects a percentage of events and drops the rest. Instead, Grepr’s signal processing engine detects repetitive, low-value patterns, forwards summaries and high-signal telemetry to Datadog, and preserves raw data in low-cost storage for backfill and incident investigation.
Can Grepr help with Datadog costs beyond logs?
Yes. Grepr also supports distributed tracing, with metrics support anticipated in summer of 2026.
How does Grepr backfill data during an incident?
Grepr can manually or automatically backfill data based on triggers such as incidents, anomalies, support tickets, or investigations.
Does Grepr preserve every log event?
Yes. Grepr sends interesting log patterns to Datadog, and preserves the noisy logs in low-cost storage for backfill and incident investigation.
How fast can we get started?
Grepr can be set up in minutes using a single configuration change that points your existing log shippers and agents to Grepr. No agents to install, no re-instrumentation, and no migrations.
Does Grepr replace Datadog data governance controls?
No. Your Datadog controls stay useful. Grepr adds an upstream layer that changes the volume and shape of telemetry before it reaches Datadog.
Save up to 90% on your Datadog bill
Show us your telemetry pattern, and we’ll show you how Grepr can reduce your noise.