Data and AI releases

548 this month · 176 companies

OpenTelemetry support for AI monitoring is now GA

Generally availableNot yet verified

No New Relic agent required. If your app already emits OpenTelemetry traces, you can now send GenAI spans directly to AI monitoring and see every LLM call, tool call, and agent step , as part of your existing distributed traces.

AI agentsLLMsObservabilityPerformance

Read on docs.newrelic.com

Also shipped Aug 31, 2026New Relic in August 2026 →

More from New RelicEvery New Relic release →

React Native symbolication support launches

New Relic now supports React Native symbolication. Apply source map files to unminify stack traces so you can see the exact line of code behind every mobile JavaScript error, and resolve issues faster. Source map support helps with: Speeding up debugging and lowering MTTR: Remove the guesswork and see the exact line of code that caused an error.

Update
Source ↗

New Relic Lens is now generally available

Today, we are excited to announce the General Availability of New Relic Lens , a powerful data federation capability designed to simplify and accelerate data discovery and analysis across multiple environments.

GA
Source ↗

New Relic Notebooks is now generally available

New Relic Notebooks is now generally available and integrated into the core New Relic platform. Notebooks let you build structured, collaborative documents that combine live telemetry queries, visualizations, and markdown text in a single workspace, ending "tab fatigue" and preserving the investigative context that disappears when an incident is over.

GA
Source ↗

Now query up to 30 New Relic accounts at once!

Today we are excited to announce that the max number of New Relic accounts that can be queried at once is increasing its limit from 5 to 30! This can be done both through the UI – by clicking "Multi-account (up to 30)" in the account dropdown – or via the API.

Update
Source ↗

Session replay now has its own billing category

New Relic now reports session replay data (both Browser and Mobile) under its own billing category in Data ingestion and usage, instead of under browser events and mobile events. This is a reporting change only: your session replay functionality, pricing, and total data ingested are unaffected.

Pricing
Source ↗