Independent New Relic support

New Relic Support for APM Agents, Distributed Tracing and Ingest Cost

Last reviewed by Tyler Eastridge

AceMQ gives New Relic teams 24/7 support for APM agents, infrastructure agents, logs and alert policies across hosts, Kubernetes and serverless. Most calls start with one of three problems: ingest volume driving the bill up, a service that stops reporting after a deploy, or distributed traces that break at a service boundary.

24/7 New Relic support with response targets from 15 minutes, by plan.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ New Relic consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week on New Relic

Seven telemetry failures we see most, each with the first query, agent log line or condition setting we check before touching anything else.

Common New Relic production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Ingest bill up with flat trafficQuery FROM NrConsumption SELECT sum(GigabytesIngested) FACET usageMetric SINCE 30 days ago to see ingest by data source. High-cardinality attributes on custom events and unfiltered Kubernetes logs are the common drivers.
Service stops reporting after a deployCheck the agent's own log for licence key or app_name errors, and for a startup order change: the Java agent attached after the framework loaded, or a Node.js require('newrelic') no longer first.
Trace breaks at a service boundaryConfirm W3C trace-context headers pass through the gateway or proxy; a header-stripping proxy or an async hop without context propagation ends the trace.
NRQL dashboards time outNarrow the SINCE window, use FACET on low-cardinality attributes and avoid SELECT * on large event types.
Alerts flappingReview condition thresholds, signal-loss settings and gap-filling strategy; an NRQL alert on sparse data without a gap strategy opens and closes constantly.
Alert missed during a real outageLook at whether the condition relied on data from the failing service itself; loss-of-signal conditions are needed for outages that stop data.
Logs ingested but nothing parsedCheck parsing rules and Grok patterns, and the logtype attribute that selects them.

Ingest changes come with a short list of what each drop rule costs you in visibility, so nobody is surprised mid-incident.

Telemetry gone quiet during an outage? Request a quote and we answer inside an hour.

Contact Us

Deployment coverage

Which New Relic setups does AceMQ support, and who covers what?

SetupWhat AceMQ coversWhat New Relic coversExcluded
APM language agents (Java, .NET, Node.js, Python, Go, Ruby, PHP)Config, attach order, sampling, transaction namingAgent defects, per your planApplication code
Infrastructure agent and Kubernetes integrationInstalls, Helm values, cluster metrics, resource useAgent defectsControl-plane faults
Logs in contextForwarding, parsing, volume reductionPlatform behaviourSource application logging
Alerts and NRQL dashboardsCondition design, workflows, query performancePlatform behaviourYour on-call process
OpenTelemetry to New RelicCollector config, OTLP export, attribute mappingOTLP intakeUpstream SDK defects

Support options

New Relic support vs independent support: an honest comparison

New Relic's support documentation lists Standard, Pro and Enterprise plans for usage-based pricing (docs.newrelic.com global technical support offerings, read 17 Nov 2026).

New Relic Standard / New Relic Pro / New Relic Enterprise
Independent support from AceMQ
P1 first responseNew Relic Standard: 2 business daysNew Relic Pro: 2 hoursNew Relic Enterprise: 1 hour
P1 first responseFrom 15 minutes, by plan
P2 first responseNew Relic Standard: 2 business daysNew Relic Pro: 6 business hoursNew Relic Enterprise: 2 business hours
P2 first responseBy plan, 24/7 on higher plans
HoursNew Relic Standard: Business hours; 24x7 follow-the-sun only for P1 business-critical casesNew Relic Pro: SameNew Relic Enterprise: Same
Hours24/7 across Americas, EMEA, APAC
PhoneNew Relic Standard: Not listedNew Relic Pro: Not listedNew Relic Enterprise: Listed with Slack
PhoneDirect to named engineers, channels by plan
ScopeNew Relic Standard: Product help and defectsNew Relic Pro: New Relic Enterprise:
ScopeOperating the estate: cost, agents, alerts
Where AceMQ is not the right fitNew Relic Standard: An agent bug needs a New Relic case; keep your plan and add AceMQ for operations and costNew Relic Pro: New Relic Enterprise:
Where AceMQ is not the right fit

What's Included

Everything in your New Relic support contract

Language agents, the Kubernetes integration, log forwarding, NRQL alerts and OpenTelemetry export, all under one contract and never billed per ticket.

  • 01

    Ingest Cost Governance

    Where your bill actually goes, by data type and source — then drop filters, sampling rates, log forwarding rules, and metric cardinality changes that cut ingest without losing the signal you rely on during an incident.

  • 02

    Emergency Incident Response

    Observability blind during an outage, agents not reporting, or alerts that did not fire. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge — including helping you debug the underlying incident, not just the tooling.

  • 03

    Instrumentation & Trace Coverage

    Agent deployment across your runtimes, custom instrumentation for the code paths that matter, and end-to-end trace context propagation across queues, gateways, and service boundaries where traces usually break.

  • 04

    Alert Quality & On-Call Hygiene

    Rebuilding noisy alert policies into conditions your on-call trusts: correct thresholds and windows, loss-of-signal detection, sensible grouping, and routing that pages the team who can actually act.

  • 05

    NRQL & Dashboard Engineering

    Dashboards built around your service-level objectives rather than agent defaults, plus NRQL query tuning and cardinality control so the queries return before your incident call ends.

  • 06

    Migration & OpenTelemetry Strategy

    Moving onto New Relic from another vendor, or onto OpenTelemetry instrumentation so your telemetry is portable. We plan and execute both, including honest advice on what you lose either way.

Why AceMQ

Why observability teams stay with us

  • We Treat Ingest Cost as an Engineering Problem

    Observability bills grow because instrumentation decisions get made once and never revisited. We audit ingest against what your teams actually query during incidents, and cut the rest — with the reduction documented so it survives the next deploy.

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your service map, your agent versions, and your alert policies — so a P1 call starts with diagnosis, not twenty minutes of you explaining your architecture.

  • We Debug the Layers the Vendor Won't

    New Relic support owns the platform. Your instrumentation, your application code, your queries, your log pipelines, and the incident the telemetry is pointing at are all outside that boundary — and all inside ours.

  • No Tier-1 Triage Layer

    You reach a senior engineer directly by phone, email, or Slack. No help desk collecting information to pass along, and no escalation approval standing between you and someone who can actually fix it.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Full-Stack, Not Just the Agent

    The interesting questions are rarely about New Relic. We diagnose across the JVM or runtime, the database, the message broker, and Kubernetes — because that is where the thing your dashboard is flagging actually lives.

What our New Relic engineers cover

Hosts, clusters and serverless functions across the three big clouds, plus sites where agents reach New Relic only through a proxy.

  • AWS (EC2, ECS, EKS, Lambda)
  • Microsoft Azure (AKS, App Service)
  • Google Cloud (GKE, Cloud Run)
  • Kubernetes & OpenShift
  • Java, .NET, Node.js, Python, Go, Ruby, PHP agents
  • OpenTelemetry collectors & OTLP ingest
  • Infrastructure & Kubernetes agents
  • Fluent Bit & log forwarder pipelines
  • Browser & mobile monitoring
  • Synthetic monitors & private minions
  • Bare metal & on-premise workloads
  • Hybrid cloud

Version coverage

Versions we support

Versions we support
ComponentWhat we support
Language agentsThe versions in your applications, including mixed fleets
Infrastructure agentLinux, Windows and containerised installs
Kubernetes integrationHelm-based installs and the cluster agents they deploy
OpenTelemetryCollector and SDK versions you export from

Escalation Path

Your first hour of a New Relic outage

When the monitoring itself is dark during an outage, the clock matters more than usual. Targets below depend on the plan you hold.

  1. From 15 min (by plan)first responseEmergencyBlind during a live incident: agents stopped reporting fleet-wide, alert notifications not leaving, or a forwarder outage losing logs
  2. 1 hourfirst responseCriticalIngest running far above plan, traces broken on a revenue path, or key alert conditions firing late
  3. 4 hoursfirst responseHighAlert conditions flapping on sparse data, NRQL dashboards timing out, one service missing after a deploy
  4. Next Dayfirst responseStandardParsing rules for a new log source, dashboard design around SLOs, OpenTelemetry rollout planning

A missing alert at 3am and a question about NRQL syntax should not share a queue, so each severity has its own clock.

Want a New Relic engineer who already knows your service map? Ask for a quote or write to us.

Contact Us

Pricing

What does AceMQ New Relic support cost?

New Relic support usually costs $24,000–72,000 a year. The figure moves with the number of instrumented services, monthly ingest volume, how many alert policies page people, and whether OpenTelemetry collectors sit alongside the New Relic agents.

All prices are in US dollars (USD). Response targets begin at 15 minutes by plan, 24/7, and we reply to quote requests within 1 hour.

Support In Practice

New Relic problems we have worked through

New Relic support work from AceMQ. Each card links to the full write-up: the services and agents involved, what AceMQ diagnosed or changed, and the result.

1 / 4 case studies

  • Remediation

    New Relic Agent Overhead Remediation

    Digital Commerce Platform

    Remediation of application latency and memory growth traced to APM agent configuration on the customer's own JVM and container estate.

    New RelicJavaKubernetesLinux
  • Support

    New Relic Distributed Tracing Support

    Insurance Services Provider

    Ongoing support for distributed tracing across a mixed New Relic and OpenTelemetry estate where traces broke at instrumentation boundaries.

    New RelicOpenTelemetryJava.NETKubernetes
All use cases

Support options

Four tiers of New Relic support.

AceMQ offers New Relic support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for agents and alerts your team runs, proactive monitoring that catches coverage gaps and ingest growth first, managed New Relic operations inside your own account, and fully managed New Relic run on your behalf from AceMQ-managed accounts and infrastructure, with the collectors and pipelines. New Relic itself stays New Relic's SaaS.

  • Tier 1

    New Relic 24/7 Support & Incident Management

    You own the account, we answer the hard calls

    Best for: Platform teams that run their own agents and alerts and want a senior engineer for outages and odd behavior.

  • Tier 2

    New Relic 24/7 Support with Proactive Monitoring

    Scheduled ingest, agent and alert reviews

    Best for: Teams whose bill or pager volume keeps creeping up and who want it checked every quarter.

  • Tier 3

    Managed New Relic on Your Infrastructure

    We run agents, forwarders and alert policies

    Best for: Organizations that keep collectors and proxies inside their own network but do not want to staff the upkeep.

  • Tier 4

    Fully Managed New Relic on AceMQ Infrastructure

    We operate your whole New Relic setup

    Best for: Small platform teams that want dashboards, alerts and cost control handled without hiring a specialist.

FAQ

New Relic support questions

Still have questions about New Relic? Email an Expert

Who provides enterprise support for New Relic?

New Relic provides support under its Standard, Pro and Enterprise plans. Independent providers such as AceMQ add 24/7 operational support: ingest cost, agents, traces and alerts. AceMQ costs $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

How is this different from New Relic's own support?

New Relic supports New Relic. We support how you use it, and we run incidents with senior engineers assigned to your account who know your estate.

Can you actually reduce our New Relic bill?

Yes, by attribution first. We break ingest down by data source, attribute and service using NrConsumption, then propose drop rules, sampling and log filters for data nobody queries. Each change is listed with the visibility it removes before anything is applied.

Why did our service stop reporting to APM after a deploy?

Typical causes are the agent loading after the framework, a changed app_name, a license key missing from the new environment, or an egress rule blocking the collector. The agent's own log usually names which one within minutes.

Our distributed traces break between services. Can you fix that?

Yes. We trace the header path through proxies, queues and async hops and fix propagation.

Do you work with OpenTelemetry instead of the New Relic agents?

Yes, including mixed estates.

Who offers New Relic consulting and professional services?

AceMQ offers an ingest and alert review, agent rollout planning and OpenTelemetry migration support as named deliverables.

How fast will you respond?

Plans with the fastest target start work within 15 minutes, any hour. Picture a Sev 1 where every Java service stopped reporting after a deploy: we join a bridge, read the agent log for license key and startup errors, and you get a written cause. P2 is 1 hour, P3 4 hours, P4 next day.

Does phone support come with every New Relic plan?

Per New Relic's documentation, phone support is listed for Enterprise. With AceMQ you reach senior engineers assigned to your account directly; the channels are set by plan.

Can we buy New Relic help for one project only?

Yes. A single engagement, such as an ingest audit, an alert rebuild or an OpenTelemetry cutover, is available without a yearly commitment. Teams that want weekend and overnight cover tend to move onto the annual plan afterward, where named engineers stay on the account.

How is a New Relic support contract priced?

Annual contracts run $24,000 to $72,000 (USD). We price against how many services and hosts carry agents, your monthly ingest, the number of alert policies and the response level you pick. Share an ingest-by-source export and a quote comes back within 1 hour.

Let's talk

Observability You Trust, at a Bill You Can Explain

Send us one month of ingest by data source and we will tell you in 1 hour which three sources to cut first.

A senior New Relic engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a New Relic Architect