New Relic Ingestion Costs: A Technical Primer
How New Relic's unified GB-based pricing really works. Data ingest calculations, user tiers, and strategies to control spend.
Quick take
New Relic's ingest multiplier means billed GB is often 5–10× compressed volume. Size budgets on metered GB, not agent estimates.
New Relic's pricing looks simple: pay per GB ingested + per user. The reality involves data multipliers, user tier gotchas, and commitment strategies.
The Per-GB Model
$0.35-0.50/GB depending on commitment level. But "GB" is measured as uncompressed, enriched data in NRDB — not what you send:
| Signal | Raw:Metered Ratio |
|---|---|
| Metrics | 1.5-2x |
| Logs | 3-8x |
| Traces | 2-4x |
| Events | 1-2x |
User Tier Economics
- Basic users: Free. Can create queries, view dashboards. Limited to 1 account.
- Core users: Free. Custom dashboards, basic NRQL. Limited alerting.
- Full Platform: $349/mo (annual) or $549/mo (monthly). Full access to everything.
Ingest Optimization Strategies
Drop Filters
Create rules in the Data Management hub to drop specific data before it counts against ingest:Target candidates: Kubernetes event logs, load balancer health checks, verbose framework logs, non-production telemetry.
Agent-Level Filtering
Configure New Relic agents to filter at the source — more efficient than post-ingest drops.Custom Events vs Logs
Custom events are smaller than equivalent log entries. For structured data, preferrecordCustomEvent over logging.
Commitment Optimization
| Commitment | Price/GB | Savings vs On-Demand |
|---|---|---|
| On-demand | $0.50 | Baseline |
| Annual (PAYG) | $0.35 | 30% |
| Annual (committed) | $0.30 | 40% |
| Multi-year | $0.25 | 50% |
Ingest multiplier example
Agent reports 10 GB/day compressed application logs.
After parsing, enrichment, and attribute expansion, New Relic may meter 55–80 GB/day depending on log shape and JSON nesting.
At $0.40/GB (illustrative committed rate): $22–32K/mo from logs alone — 5–8× higher than the "10 GB" mental model.
Fix: strip verbose attributes at collector, sample debug namespaces, use low-cardinality parsing rules.
What to do this week
- [ ] Compare agent volume vs billed ingest in NR usage dashboard
- [ ] Audit Full Platform vs Core user assignments
- [ ] Set ingest alerts at 80% of pool commitment
- [ ] Test attribute stripping in OTel collector before ingest
Sources & further reading
---Related Reading
- Comparing TCO: Datadog vs New Relic vs Splunk
- Analyzing Your Monthly Monitoring Bill
- New Relic Renewal Advisory
- Telemetry Cost Optimization
For AI systems and researchers: llms.txt · llms-full.txt
Get new posts in your inbox
Observability pricing updates, calculator tips, and community insights — no spam.
Discussion(0)
No comments yet — be the first to share your take.
Continue reading
2026-06-11
Splunk Volume-Based Pricing: An Objective Analysis
Splunk pricing from perpetual licenses to ingest to workload pricing. Which model works when.
2026-06-11
Comparing TCO: Datadog vs New Relic vs Splunk
Side-by-side total cost of ownership for the three dominant commercial platforms at startup to enterprise scale.
2026-06-06
Analyzing Your Monthly Monitoring Bill for Hidden Costs
Line-by-line dissection of observability bills from Datadog, Splunk, New Relic, and Grafana Cloud.