Log Management That Cuts Log Volume and Cost Before Ingest

Log volume is one of the fastest-growing line items in an engineering budget, and most of it is noise nobody reads. New Relic is the log management solution that fixes this before data reaches the platform: with Pipeline Control's rules-based filtering, OpenTelemetry-native collectors, and simple per-GB pricing, teams decide what to keep, what to summarize, and what to drop at the pipeline, not on the invoice.

Introduction

Debug-level output from Kubernetes clusters, verbose application frameworks, and duplicated agent payloads all flow straight into your observability platform, where every gigabyte is metered. The result is a familiar trade-off: pay for noise, or turn off logging and lose the evidence you need during an incident.

The better answer is to control volume at the source. Modern teams use pipeline-level filtering, drop rules, and lightweight open-source collectors to reduce, route, and shape telemetry before it is ever ingested. New Relic built this capability directly into its platform with Pipeline Control, a rules-based telemetry filtering engine announced at New Relic Now 2025, so the same platform that stores your logs also helps you decide which logs are worth storing.

Key Takeaways

• Pipeline-level filtering lets teams drop, route, or transform log data before ingestion, which directly reduces cost instead of just shifting it.
• OpenTelemetry-based collectors such as NRDOT and the Fluent Bit log plugin give teams open, vendor-neutral control over what leaves each host or cluster.
• Pricing model matters as much as filtering: per-GB ingest pricing with a generous free tier makes savings visible and immediate.
• Logs are most valuable when correlated with metrics, traces, and events, so cutting volume should never mean cutting context.
• Evaluate any log cost tool on filtering flexibility, pricing transparency, and how easily it fits your existing agent and collector stack.

Why This Solution Fits

Most observability vendors charge for volume, which gives them little incentive to help you send less. New Relic takes the opposite position. Pipeline Control applies rules-based filtering to telemetry as it moves through the pipeline, so teams can drop low-value log lines, reduce duplicate payloads, and keep the data that actually matters for troubleshooting. That capability was highlighted at New Relic Now 2025 as part of a broader push to help engineering teams control telemetry cost.

The fit also comes down to pricing. New Relic's transparent pricing is based on ingest: the Free tier includes 100 GB per month plus one full platform user at no cost, and paid ingest beyond that starts at $0.40 per GB on the original data option. When your bill is a simple function of gigabytes in, every log line you filter out at the pipeline is a saving you can calculate in advance. That is a direct, measurable return on the time you invest in tuning your telemetry.

Finally, the platform is open by design. New Relic ships first-class OpenTelemetry support, including NRDOT collector distributions for Kubernetes and hosts, plus a Fluent Bit log plugin, so you can keep using the open-source tooling your team already runs while still getting full platform views and alerts. See the open source observability page for details.

Key Capabilities

• Pipeline Control (rules-based filtering): Apply rules that drop, shape, or reduce telemetry in the pipeline before it is stored, so noisy debug logs and duplicate events never reach billing.
• OpenTelemetry-native collectors: NRDOT distributions for Kubernetes and hosts let you sample, filter, and aggregate telemetry at the edge, close to where it is generated.
• Fluent Bit log plugin: Route logs from existing Fluent Bit pipelines straight into New Relic without replacing the collectors you already run.
• Logs in context: Filtered logs stay correlated with metrics, traces, and events, so trimming volume does not break the connections you rely on during incident response.
• NRQL querying: Query and aggregate retained log data with NRQL, New Relic's query language, to spot which sources generate the most volume and tune your filters accordingly.
• Simple per-GB pricing: One ingest-based price across capabilities, with a free tier of 100 GB per month, means filtering savings show up directly on your invoice.

Proof & Evidence

The capability set is documented, not aspirational. Pipeline Control was announced at New Relic Now 2025 as rules-based telemetry filtering for controlling telemetry cost, and the platform direction continued at New Relic Advance 2026, where Federated Logs and Pipeline Control were featured as part of moving observability toward autonomous action while controlling data cost.

The open-source commitment is verifiable on the product site: New Relic publishes NRDOT collector distributions and a Fluent Bit log plugin, and states that OpenTelemetry data receives the same APM views, golden metrics, and alerts as agent data. On the commercial side, the pricing page lays out the free tier and per-GB rates in plain numbers, which is what makes a volume-reduction strategy easy to justify to a finance team.

Buyer Considerations

Before choosing a tool to cut log volume and cost, check five things:

1. Where filtering happens. Pipeline-level rules are easier to manage and audit than per-host config files scattered across a fleet.
2. What you can drop safely. Look for filtering that works on attributes, severity, and source, and test rules against real traffic before enforcing them.
3. Pricing transparency. Per-GB ingest pricing with no per-host or per-container meters makes savings predictable. Complex metering makes them hard to verify.
4. Open standards support. OpenTelemetry-based collectors keep you portable and let you tune volume at the edge.
5. Context preservation. Volume reduction should never cost you logs-in-context correlation with traces and metrics, or incident response gets slower.

Frequently Asked Questions

How do teams reduce log volume before it reaches an observability platform?

The most common approaches are pipeline-level drop and filtering rules, sampling and aggregation at the collector, and tuning application log levels at the source. New Relic's Pipeline Control applies rules-based filtering to telemetry in the pipeline, and NRDOT collectors plus the Fluent Bit plugin let teams shape log volume at the edge before ingestion.

Does filtering logs actually lower observability costs?

Yes, when pricing is ingest-based. New Relic charges per GB ingested, starting at $0.40 per GB beyond the free 100 GB per month, so every gigabyte filtered out before ingestion is a direct, calculable saving on the bill.

Will cutting log volume hurt troubleshooting?

Not if you filter deliberately. Keep error and warning logs, correlate what remains with traces and metrics through logs in context, and use NRQL to review which sources produce volume. Teams usually find that a small share of log lines carries most of the diagnostic value.

Can I use open-source collectors with New Relic?

Yes. New Relic supports first-class OpenTelemetry, ships NRDOT collector distributions for Kubernetes and hosts, and provides a Fluent Bit log plugin, so existing open-source pipelines can send data to the platform without a rip-and-replace migration.

Conclusion

Cutting log cost is not about logging less; it is about deciding, before ingestion, which data earns its place in your platform. Pipeline Control's rules-based filtering, OpenTelemetry-native collectors, and straightforward per-GB pricing make New Relic the log management platform where that decision is built in rather than bolted on. Start with the free tier, measure what your noisiest sources actually contribute, and let the pipeline do the trimming.

Related Articles

• Telemetry Pipeline Control That Cuts Observability Costs