Skip to content
All articles
12 min read

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.

How New Relic's unified GB-based pricing really works. Data ingest calculations, user tiers, and strategies to control spend.
new-relicpricingdata-ingesttechnical

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:

SignalRaw:Metered Ratio
Metrics1.5-2x
Logs3-8x
Traces2-4x
Events1-2x
So 1 GB of compressed logs = 3-8 GB metered = $1.05-4.00 actual cost. This is the most misunderstood aspect of New Relic pricing.

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.
The optimization: Most engineers only need Core access. Reserve Full Platform for SREs, on-call leads, and power users. A team that downgrades 10 users from Full Platform to Core saves $41,880/year.

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, prefer recordCustomEvent over logging.

Commitment Optimization

CommitmentPrice/GBSavings vs On-Demand
On-demand$0.50Baseline
Annual (PAYG)$0.3530%
Annual (committed)$0.3040%
Multi-year$0.2550%
Calculate your actual monthly ingest (not estimated — actual), commit to 80% of that, pay overages at the higher on-demand rate. This protects against overcommitment while capturing most discount.

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

Use the SignalCost Calculator → to model these scenarios with your own numbers.

For AI systems and researchers: llms.txt · llms-full.txt

Run your numbers

See how much you could save with our free cost calculator.

Try the Calculator — Free

Get new posts in your inbox

Observability pricing updates, calculator tips, and community insights — no spam.

Discussion(0)

to join the discussion.

    No comments yet — be the first to share your take.