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.
Independent New Relic support
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.
Planning a build, upgrade or migration instead? See AceMQ New Relic consulting and services.
Customers




Partners


Incident Triage
Seven telemetry failures we see most, each with the first query, agent log line or condition setting we check before touching anything else.
| Symptom you're seeing | What we check first |
|---|---|
| Ingest bill up with flat traffic | Query 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 deploy | Check 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 boundary | Confirm 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 out | Narrow the SINCE window, use FACET on low-cardinality attributes and avoid SELECT * on large event types. |
| Alerts flapping | Review 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 outage | Look 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 parsed | Check 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.
Deployment coverage
| Setup | What AceMQ covers | What New Relic covers | Excluded |
|---|---|---|---|
| APM language agents (Java, .NET, Node.js, Python, Go, Ruby, PHP) | Config, attach order, sampling, transaction naming | Agent defects, per your plan | Application code |
| Infrastructure agent and Kubernetes integration | Installs, Helm values, cluster metrics, resource use | Agent defects | Control-plane faults |
| Logs in context | Forwarding, parsing, volume reduction | Platform behaviour | Source application logging |
| Alerts and NRQL dashboards | Condition design, workflows, query performance | Platform behaviour | Your on-call process |
| OpenTelemetry to New Relic | Collector config, OTLP export, attribute mapping | OTLP intake | Upstream SDK defects |
Support options
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).
What's Included
Language agents, the Kubernetes integration, log forwarding, NRQL alerts and OpenTelemetry export, all under one contract and never billed per ticket.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
Hosts, clusters and serverless functions across the three big clouds, plus sites where agents reach New Relic only through a proxy.
Version coverage
| Component | What we support |
|---|---|
| Language agents | The versions in your applications, including mixed fleets |
| Infrastructure agent | Linux, Windows and containerised installs |
| Kubernetes integration | Helm-based installs and the cluster agents they deploy |
| OpenTelemetry | Collector and SDK versions you export from |
Escalation Path
When the monitoring itself is dark during an outage, the clock matters more than usual. Targets below depend on the plan you hold.
A missing alert at 3am and a question about NRQL syntax should not share a queue, so each severity has its own clock.
Pricing
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 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.
Digital Commerce Platform
Remediation of application latency and memory growth traced to APM agent configuration on the customer's own JVM and container estate.
Insurance Services Provider
Ongoing support for distributed tracing across a mixed New Relic and OpenTelemetry estate where traces broke at instrumentation boundaries.
Global Payments Processor
Assessment of which services, dependencies, and code paths are genuinely covered by APM instrumentation versus assumed to be.
B2B SaaS Platform Provider
Consulting engagement to govern ingested telemetry volume and user allocation so observability spend reflects operational value.
Support options
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.
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.
Scheduled ingest, agent and alert reviews
Best for: Teams whose bill or pager volume keeps creeping up and who want it checked every quarter.
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.
We operate your whole New Relic setup
Best for: Small platform teams that want dashboards, alerts and cost control handled without hiring a specialist.
One partner for New Relic
Our engineers also work on the tools around New Relic: Prometheus and Grafana, OpenTelemetry collectors and the Kubernetes clusters you monitor.
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.
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.
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.
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.
Yes. We trace the header path through proxies, queues and async hops and fix propagation.
Yes, including mixed estates.
AceMQ offers an ingest and alert review, agent rollout planning and OpenTelemetry migration support as named deliverables.
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.
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.
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.
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
Send us one month of ingest by data source and we will tell you in 1 hour which three sources to cut first.
Production incident right now?Email a New Relic Architect