Learning Objectives
- Describe what New Relic AI does and why observability matters for modern software teams
- Explain how AI is applied to correlate telemetry and assist incident response
- Identify where the platform's genuine root-cause correlation ends and its bolder autonomy marketing begins
What Is New Relic AI?
New Relic AI is the artificial-intelligence layer built into New Relic, a full-stack observability platform that engineering and operations teams use to monitor the health of their software. New Relic collects telemetry — metrics, events, logs, and traces — from applications, infrastructure, and services, then helps teams understand what is happening and why. Founded in 2008 and headquartered in San Francisco, New Relic has been a private company since a 2023 take-private transaction, so it no longer trades on a public exchange.
In its 2026 push, New Relic repositioned around agentic AI. Two capabilities anchor that story: Knowledge, which correlates live telemetry with prior incidents, recent changes, and service relationships to give context; and Autopilot, an AI site-reliability agent that triages alerts, investigates likely root cause, and scopes possible remediation. The platform also exposes a Model Context Protocol (MCP) hub so AI assistants and agents can connect to its data.
💡Key Concept
Observability and Site Reliability Engineering (SRE): Observability is the practice of instrumenting software so its internal state can be understood from the outside through metrics, logs, and traces. Site reliability engineering is the discipline of keeping production systems available and performant — responding to incidents, reducing toil, and preventing repeat failures. Observability tools are the SRE's primary instrument panel.
What New Relic AI Does
- Telemetry correlation — the Knowledge capability ties current signals to past incidents, recent deployments, and service dependencies so an alert arrives with context rather than in isolation
- Alert triage — the Autopilot agent sorts and prioritizes incoming alerts to reduce the noise on-call engineers face
- Root-cause investigation — it walks the connected telemetry to surface probable causes of an outage or degradation
- Remediation scoping — it proposes and frames possible fixes for a human to review
- MCP hub — an integration point that lets external AI assistants and agents query New Relic's observability data
How AI Is Applied
The most grounded and genuinely useful AI in New Relic is the root-cause correlation. Correlating a spike in errors with a recent code change, a related service's degradation, and a similar past incident is exactly the kind of pattern-matching across large, messy telemetry that machine learning does well — and it maps directly onto how an experienced engineer reasons about an outage. That work is real and valuable.
The Autopilot SRE agent extends this toward autonomy: triaging, investigating, and scoping remediation with less human input. This is where honest framing matters. New Relic's 2026 messaging leans heavily on the word "agentic," and the boldest claims about autonomous investigation and action should be read with mild skepticism. Automated triage and AI-assisted investigation are believable and demonstrably helpful; fully hands-off remediation in complex production environments is a harder bar. Teams should treat the AI as a fast, well-informed assistant that accelerates the human on-call process, and validate how much it actually decides versus recommends before relying on it.
Who Uses New Relic AI
New Relic AI is used by software engineering teams, DevOps and platform engineers, and site-reliability engineers at organizations that run production software at scale. It appeals to teams already invested in observability who want to shorten the time from alert to diagnosis, and to on-call staff who want context and a first-pass investigation delivered automatically rather than assembled by hand under pressure.
Pricing
New Relic uses consumption-based pricing built around the volume of telemetry data ingested and the number of users, with tiers that layer in advanced and AI features. Specific costs depend on data volume, retention, and the capabilities enabled, so pricing is quote-based for larger deployments. Organizations contact New Relic directly for enterprise terms.
Company Details
| Detail | Info |
|---|---|
| Company | New Relic |
| Founded | 2008 |
| Headquarters | San Francisco, California |
| Ownership | Private (taken private in 2023) |
| Category | Observability and site reliability engineering |
| Key AI Features | Knowledge (telemetry correlation), Autopilot (AI SRE agent), MCP hub |
| Website | newrelic.com |
Strengths
- Full-stack observability — one platform spanning applications, infrastructure, logs, and traces
- Grounded correlation — tying telemetry to past incidents, changes, and service relationships is a genuine, high-value use of AI
- Faster incident response — automated triage and investigation can shorten the path from alert to root cause
- Open integration — the MCP hub lets external AI assistants and agents work against New Relic's data
- Established platform — a mature vendor with broad instrumentation coverage across languages and technologies
Limitations and Considerations
- Agentic marketing outpaces reality — the boldest autonomy claims deserve mild skepticism; verify what the agent decides versus recommends
- Consumption pricing — data-volume-based billing can be hard to predict and requires monitoring to control cost
- Human oversight still essential — remediation in complex production systems should stay under human review
- Value depends on instrumentation — the AI is only as good as the telemetry it can correlate, so coverage gaps limit results
Key Takeaways
- New Relic AI is the agentic layer of New Relic's full-stack observability platform, centered on the Knowledge correlation capability and the Autopilot SRE agent
- Its root-cause correlation — linking live telemetry to past incidents, changes, and service relationships — is a genuine and valuable application of AI
- The heavy 2026 "agentic" repositioning means the boldest autonomy claims should be read with mild skepticism and validated in practice
- Best for engineering and SRE teams already invested in observability who want AI-accelerated incident triage and investigation


