This blog post shows how to reduce log volume by up to 90% by integrating New Relic with Grepr. Using a simple Docker-based microservices demo, we walk through configuring Fluent Bit to ship logs to New Relic, then show how easily Grepr can be inserted into the pipeline to intelligently filter out noise. The result is cleaner, more actionable log data, reduced observability spend, and no disruption to existing workflows. All raw data is retained in low-cost storage and can be backfilled on demand—helping teams stay in control of both their visibility and their budget.
More blog posts
All blog posts
Events
KubeCon Amsterdam 2026: Hallway Conversations Said What Keynotes Didn't
KubeCon EU 2026 made one thing clear: AI infrastructure is generating telemetry volumes that most observability budgets were never built to handle.
Engineering Guides
How to Drop Noisy Health Check Logs Before They Hit Your Observability Platform
Healthcheck logs generate millions of identical lines per day and silently inflate your observability bill, but filtering them at the right layer can cut total log volume by 15 to 40 percent.
.png)
Comparisons
New Relic Pipeline Control vs Grepr: Manual Rules vs AI Automation
New Relic Pipeline Control bills you on data volume before any filtering happens, requires manual YAML config for every pipeline, and needs a separate Kubernetes install per environment.
Get started free and see Grepr in action in 20 minutes.
