Running New Relic?

New Relic bill climbing every month? We bring it back.

New Relic's ingest-priced model means every custom event, every verbose log line and every forgotten environment adds to the monthly bill. We take over accounts where the usage meter is running hotter than expected, where the APM agents are reporting intermittently, and where a dashboard that used to answer the question in one chart now needs ten.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

newrelic-agent.log

still broken

What it is

New Relic at a glance

New Relic is an observability platform founded in 2008 by Lew Cirne and now listed as New Relic, Inc. (acquired by Francisco Partners in 2023). The product covers APM agents for most mainstream languages, infrastructure monitoring, browser and mobile real user monitoring, synthetics, logs and traces, with NRQL (New Relic Query Language) as the query layer across all of it.

In 2020 the company moved to a usage-based pricing model called New Relic One, charging on data ingest in gigabytes plus full-platform users. That change made New Relic cheaper for small teams and more expensive for anyone who turned on verbose logging or sent every custom event, which is why most of the accounts we see have a Usage tab everyone is slightly afraid of.

Type
Observability platform (APM, infrastructure, logs, synthetics)
First released
2008
License
Proprietary SaaS, Apache 2.0 for most language agents
Maintained by
New Relic, Inc.
Typically used for
Application performance monitoring, infrastructure metrics, log aggregation, synthetic checks, browser and mobile RUM

The honest version

New Relic pros and cons

No technology is all upside. This is where New Relic earns its place and where it tends to cause trouble.

Where New Relic is strong

  • One platform across signalsAPM traces, infrastructure metrics, logs, browser timings and synthetics all live in the same account with one query language, so correlating an error trace with its deploy and its host metrics is one tab rather than three tools.
  • NRQL is powerful and consistentA single query language runs across events, metrics, logs and traces, with funnels, percentiles and faceting built in. Dashboards and alerts share the same syntax.
  • Language agents are matureThe agents for Java, .NET, Node, Python, Ruby, Go and PHP have been in production for years, and the instrumentation of mainstream frameworks is deep by default.
  • OpenTelemetry is a first-class inputYou can send OTLP directly from applications or from the OpenTelemetry Collector into New Relic without the vendor-specific agent, which keeps you portable.
  • Alerts and SLOs are integratedAlert conditions, incident intelligence and service-level objectives sit next to the data they are monitoring, which removes the need for a separate alerting product in many shops.

Where New Relic bites

  • Ingest pricing surprises teamsA log pipeline turned up to debug, a custom event instrumented on every request, or a new environment pointed at the same account can double the monthly data ingest without a code deploy anywhere.
  • The feature surface is wide and confusingEntity explorer, Workloads, Lookouts, Services, Hosts, APM, Browser and Mobile each have their own navigation, and new engineers spend weeks working out where the data they want actually lives.
  • Agent configuration drifts across servicesTransaction naming rules, custom attributes and sampling live in agent config files, environment variables and the server-side UI. A production fleet ends up with slightly different settings per service and nobody can tell you why.
  • Retention tiers surprise on NRQLDifferent event types have different retention windows, and a query that ran last month returns no data this month because the event type was downsampled or expired. Learning the tiers is part of the job.
  • Datadog comparison is always on the tableTeams evaluating observability almost always also look at Datadog, and the feature parity debate is close enough that the choice often comes down to pricing model and existing contracts rather than capability.
  • Browser agent and CSP interact awkwardlyThe browser agent still needs permissions that strict Content Security Policy headers block, and getting it working on a tight CSP without unsafe-inline takes real work.

Sound familiar?

Common New Relic problems we fix

The New Relic problems that bring people to us, and what you have once each one is fixed.

estimated monthly: $9,840 (budget $4,000)

The ingest bill has run away

A forgotten verbose log level in staging, a custom events pipeline firing on every request, or a new infrastructure fleet whose agents were installed with defaults. The usage tab tells the story if you know how to read it.

Ingest in line with the plan

APM agent: license key is no longer valid

APM agents stopped reporting

A license key rotation during an account move, or a Kubernetes deployment that still carries the old key as a baked-in env var. Services continue to run but produce no APM data.

Agents reporting on current keys

Transaction naming rule did not match

Transaction names have exploded

An agent that includes a UUID in the default route name, producing thousands of distinct transactions. The APM overview becomes useless and query performance suffers.

Transactions grouped as they should be

logs API: dropped events (rate limit)

Log events are being dropped

A logging pipeline that fans out faster than the account rate limit, with no batching. Investigating an incident reveals that the exact window you want is where the drops happened.

Logs delivered without drops

alerts: muted for 45 days

Alerts have been muted and forgotten

A policy muted during an unrelated incident and never reactivated. The condition still exists, but nothing is firing, and the thing it was meant to catch has been happening quietly.

Alert hygiene restored

NRQL query: event type retention limited

Dashboards show gaps on old data

A dashboard built against an event type whose retention is 8 days on the current plan, where the queries reach for 30 days. Users assume the data is wrong rather than the query.

Queries and retention aligned

nrdot collector: 429

OpenTelemetry collector is being rate limited

An OTel Collector configured to batch at too large a size, or too high a flush rate, hitting the account's ingest rate limits and dropping spans at the edge.

Collector tuned and stable

Synthetic monitor: timeout 30s

Synthetic monitors fail intermittently

A monitor pointed at an endpoint that occasionally exceeds the 30s timeout, or a script monitor whose selectors age out as the page changes. False alarms accumulate and the real ones get ignored.

Monitors reflecting actual availability

What we do

New Relic help, from rescue to steady state

Call us for one runaway ingest, or hand us the whole account.

Rescue
A New Relic bill that has climbed above budget, agents that stopped reporting during a deploy, or a dashboard that shows nothing during the incident. We stabilize the account first and then explain the cause.
Cost control
A sweep through what is actually being ingested, with drop rules, sampling and retention tiers tuned against the questions the business actually asks, and the before and after numbers on paper.
Agent hygiene
APM and infrastructure agents brought onto consistent configuration, with transaction naming rules, custom attributes and sampling defined in code rather than clicked into the UI per service.
NRQL and dashboards
Dashboards rebuilt against the questions your teams actually ask, with NRQL queries that fit the retention tier they are querying and alerts that fire when they should.
OpenTelemetry migration
Moving from vendor agents onto OTLP where it makes sense, so instrumentation is portable and the New Relic account is one consumer rather than the only one that can read the data.
Managed Tech
Monthly ingest review, agent and OTel Collector patching, dashboard and alert upkeep, and someone on hand when the bill spikes before anyone can explain why.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running New Relic alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

New Relic questions

Something else? Call+1 737 727 7327

Why has our New Relic bill gone up this month?

New Relic bills on data ingest in gigabytes, so the bill grows whenever logging gets more verbose, more custom events fire, or more infrastructure agents start reporting. The Usage tab breaks ingest down by event type and account, and the honest first move is to identify which event type grew and whether the data is actually being queried. Most accounts can halve their bill once drop rules and retention tiers match actual use.

New Relic or Datadog, which should we pick?

The feature overlap is close enough that for most teams the answer comes down to pricing model and existing commitments. Datadog's per-host plus per-feature pricing is easier to predict and gets expensive fast at scale; New Relic's ingest-based pricing is cheaper for small teams and unpredictable without discipline. We will look at your actual data shape and tell you honestly which lands cheaper for the next twelve months.

Why are our APM agents not sending data?

Usually a license key rotation that did not propagate, a firewall that blocks the collector endpoint on a new environment, or an application framework whose instrumentation is not automatic. The agent logs tell you which. We sweep the fleet, consolidate the license key handling, and confirm every service is reporting with the correct account.

Should we move from New Relic agents to OpenTelemetry?

For most backend services, yes. OTel instrumentation is portable, the OpenTelemetry Collector lets you fan out to multiple backends, and New Relic accepts OTLP directly. We usually keep the New Relic infrastructure agent for host metrics and move application instrumentation onto OTel, then review whether the full agent is still needed.

Can you take over a New Relic account from another team?

Yes. We rotate the account owner and license keys, audit which services and hosts are reporting, consolidate dashboards and alerts that have drifted, and bring the ingest in line with what the business actually uses. Nothing silently stops reporting during the handover.

How much does New Relic help cost?

Our quotes are free. Describe the account size, the signals you ingest, and what is going wrong, and we return a price before any configuration change is made.

Free estimate

New Relic giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.