49:"SourceReleaseList" 4a:I[185801,["$2","$3","$4","$5","$6","$7","$e","$f","$10","$11","$12","$13"],"$49"] 4b:T51c,Today, we're thrilled to announce the general availability of our new OCI monitoring integration. This expansion of our infrastructure monitoring portfolio introduces out-of-the-box telemetry ingestion for OCI metrics and logs, bringing Oracle Cloud observability directly into New Relic for the first time. With this release, multi-cloud enterprises no longer have to manage OCI in a silo. By bringing OCI metrics and logs into a single platform alongside AWS, Azure, and GCP, you can break down operational silos, eliminate multi-cloud coverage gaps, and accelerate root-cause analysis across your entire cloud footprint. ## What's new in this release - **Native OCI Observability**: Ingest, query, and alert on performance metrics and logs from key OCI resources, including Compute, Storage, Database, and Network services. - **Co-located Cloud Telemetry**: View and analyze your OCI performance metrics right alongside your existing AWS, Azure, and Google Cloud telemetry. - **Multi-Cloud Troubleshooting**: Monitor and trace performance across all your cloud providers in one platform to identify and resolve cross-environment issues. Get started with our [OCI integration guide](https://docs.newrelic.com/docs/infrastructure/oci/introduction/) and begin streaming your Oracle Cloud telemetry today!4c:T98d,## Performance Risks Inbox is GA Performance Risks Inbox is now generally available (GA). It finds the performance anti-patterns that quietly slow your application down, such as N+1 queries and inefficient database calls, and groups them in one place so your team can fix them before they become incidents. If you're new to it, the [Public Preview announcement](https://docs.newrelic.com/whats-new/2026/05/whats-new-05-14-performance-risks-inbox/) covers the fundamentals and the full list of risks it detects. Your feedback during the preview shaped four additions that ship with GA. ## What's new at GA - **Account-level overview**: A new [overview page](https://docs.newrelic.com/docs/triage-inbox/performance-risks/access-and-use/#overview) shows which entities in an account carry risk, how that risk is distributed, and which resolving entities may have the highest impact, so you can go straight to what needs attention instead of checking entities one by one. - **Workloads support**: Performance Risks now appear alongside errors in both [Standard and Intelligent Workloads](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#performance-risks). You can see risk across a whole user journey, such as checkout, and move between a workload, the entities inside it, and the global view. - **AI-generated insights**: Select [Generate insights](https://docs.newrelic.com/docs/triage-inbox/performance-risks/access-and-use/#recommendations) on a risk group to get a plain-language summary of the likely root cause across all of its occurrences, along with a suggested direction for the fix. AI insights are optional and become available once your organization administrator has enabled New Relic AI capabilities. - **MCP server support**: The [New Relic MCP server](https://docs.newrelic.com/docs/triage-inbox/performance-risks/access-and-use/#using) now supports Performance Risks Inbox, so you can ask about your Performance Risks from the AI assistant or IDE you already use, without switching to the New Relic UI. ## Get started You'll find Performance Risks Inbox in your APM and Browser entity views, as well as in Triage Inbox and Workloads. To learn more, see [Introduction to Performance Risks Inbox](https://docs.newrelic.com/docs/triage-inbox/performance-risks/introduction/). Your feedback continues to drive our roadmap, so let us know what you'd like to see next.4d:Tafe,## Create and define Intelligent Workloads Intelligent Workloads is now generally available (GA), designed for teams that want to proactively monitor business-impacting transactions and associated KPIs. You can now leverage bulk creation to build multiple workloads at once. Customers who want to scope their Intelligent Workloads can now use exclude filters to prune unwanted dependency paths. - **Bulk workload creation**: You can now create multiple Intelligent Workloads at once using the [bulk create](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/create-intelligent-workload/#bulk-create) option in the recommendations modal. New Relic automatically surfaces candidate transactions based on processing time, latency, or error rates so you can quickly curate and spin up workloads in bulk. - **Workloads Scoping**: [Exclude filters](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/create-intelligent-workload/#exclude-filters) allow you to prune unowned microservices, third-party APIs, or irrelevant pipeline branches from your Intelligent Workload dependency graph. Defining target entities and pruning directions ensures future trace paths automatically filter out unwanted dependencies without requiring manual maintenance. ## Improvements to Standard Workloads Standard Workloads now shares the same context-rich summary page structure as Intelligent Workloads, bringing both experiences closer to feature parity. Customers who want to define Standard Workload health using alert policies and conditions can now do so directly. The updated Standard Workload [summary page](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/use-workloads/#health) provides a central operational dashboard with richer contextual data during active investigation. We recommend starting with the **What's Changed** timeline when a workload status shifts to view recent deployments, error group spikes, or alert activity. From there, you can filter directly to entities in **Critical** or **Warning** states and review their aggregated golden metrics to see if an error rate or latency spike is driving the degradation. This structured flow helps you pinpoint performance issues before you jump to an individual entity details page. Standard Workloads now support custom [alert policies and conditions](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/workload-status-configuration/#alert-policy-conditions), bringing health configuration to full parity with Intelligent Workloads. You can reuse existing alert conditions or KPIs to set workload health directly from active alert states. This eliminates manual rule setup and ensures your workload status aligns with your team's established monitoring thresholds.4e:T525,You can now define, manage, and provision your New Relic Notebooks using Terraform. This lets you maintain notebooks in version control, review changes in pull requests, and deploy them alongside the rest of your infrastructure code. ## Key features - **Full CRUD support:** Create, read, update, and delete New Relic Notebooks as a native Terraform resource. - **Access management:** Configure user permissions to safely control notebook creation and editing across your organization. - **Programmatic access:** Use the full CRUD API and Blob Storage API to build automated notebook workflows and AI agent integrations. ## Get started To start managing your notebooks with infrastructure as code, check out the resources below: - Explore the [Terraform Registry documentation](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/notebook) for schema references and example configurations. - Review the [Notebooks permissions documentation](https://docs.newrelic.com/docs/query-your-data/explore-query-data/notebooks/introduction-notebooks/#notebooks-permissions) to set up proper user access. - Read the [Notebooks Blob Storage API guide](https://docs.newrelic.com/docs/query-your-data/explore-query-data/notebooks/blob-storage-api-for-notebooks/) to build automated agent workflows.4f:T535,New Relic is excited to share that Scheduled Search and Reporting is now generally available. Instead of manually re-running the same NRQL query to check on your data, Scheduled Search runs it for you, on whatever cadence you choose, and delivers the results straight to your inbox. ## What is Scheduled Search and Reporting? Scheduled Search and Reporting lets you take any NRQL query and run it automatically on a recurring schedule: hourly, daily, weekly, or a custom cadence you define. It's built for the reports and checks you'd otherwise have to remember to run yourself: a daily error summary, a weekly top N breakdown, a recurring compliance or usage report. Set it up once, and New Relic keeps delivering fresh results on time, every time. ## Notification conditions Not every scheduled query needs to land in your inbox on every run; often you only care when something looks wrong. With **Notification Conditions**, you can attach a condition based on the total number of results returned by the NRQL query (for example, when the result count equals, is greater than, or matches another specified threshold). This ensures you are notified only when the query results meet your defined criteria. Learn more about [Scheduled Search and Reporting](https://docs.newrelic.com/docs/nrql/using-nrql/schedule-nrql-searches/).50:T82c,Pipeline Control pipelines used to ship with a static, fixed structure — one Sample Rate node, one Filter node, one Transform node, in a set order. Now you can add and delete Sample Rate, Filter, and Transform processors at any point in the pipeline, in any order, as many times as you need. ## What you get - **No more fixed layout** — Insert a Sample Rate, Filter, or Transform node at any point along the pipeline using the **+** control between two nodes, instead of being limited to one of each in a preset position. Stack multiple Filter or Transform nodes back to back, or sample before and after a transform — whatever order your data needs. - **Write OTTL by hand or start from a recipe** — Transform and Filter rules are backed by real OpenTelemetry Transformation Language (OTTL) statements. Use the built-in recipes to pre-fill common conditions and statements, or write your own from scratch, and preview exactly how a rule reshapes a sample payload before you save it. - **Draft, save, and deploy on your terms** — Changes to a pipeline are staged as a new draft version. Save your draft, preview the generated OTel YAML, and only push it live when you're ready with **Create Deployment**. - **Delete a processor from anywhere in the chain** — Added a node for testing, or no longer need one in the middle of the pipeline? Delete it from wherever it sits on the map, save the draft, and redeploy. Nodes don't have to stay in their original slot, or stay at all. ## Get started Open **New Relic Control > Pipeline Control > Pipelines**, select a pipeline, and use the **+** control between any two nodes — anywhere along the chain — to add a Sample Rate, Filter, or Transform step. Define your condition and OTTL statement (or pick a recipe), save your draft, and click **Create Deployment** to roll it out to your fleet. To remove a processor, select its delete icon wherever it sits in the pipeline, save the draft, and deploy again. To learn more, see [Gateway UI guide](https://docs.newrelic.com/docs/new-relic-control/pipeline-control/gateway/ui-guide).51:Tc19,The updated version of Pathpoint is now available in Public Preview. When something breaks in a complex system, sometimes the hardest part isn't fixing it, but figuring out how it may impact the business and what part of the customer journey to look at first. Pathpoint helps map your technical health to your customer business journeys, such as checkout, onboarding, and in-store payments. Instead of staring at a list of service alerts, you see exactly which stage of the customer journey is degraded and what business metric might be moving because of it. When payment latency spikes, Pathpoint tells you the Checkout stage is unhealthy, cart abandonment is climbing, which microservice in the dependency chain is failing, and which team owns it. The SRE has a clear starting point. Incident communicators and business stakeholders can see what the incident affects and why it matters, without waiting on a bridge call to find out. ## Programmatic access: Terraform and NerdGraph The updated version of Pathpoint now exposes a full NerdGraph API and Terraform provider, so teams that run infrastructure-as-code workflows can create, version, and deploy Pathpoint flows the same way they manage everything else — through pull requests, code review, and CI/CD pipelines. No more one-off manual setup in the UI that lives outside your standard deployment process. Existing generally available Pathpoint users can export their current configuration directly as Terraform, migrating to the updated version of Pathpoint without rebuilding from scratch. ## Contextual business KPIs KPIs in the updated version of Pathpoint surface business metrics — orders placed, cart abandonment, and conversion rate — directly alongside technical health, so you can see whether a service degradation is actually moving a business number. KPIs work at two levels. Flow-level KPIs represent the health of the entire journey — total checkout value, overall conversion rate — with trend lines and period-over-period comparisons so anomalies are obvious without further analysis. Stage-level KPIs scope to where they belong: cart abandonment on the Checkout stage, open rate on Email Confirmation, and successful logins on Authentication. For deeper analysis, a dedicated KPIs page provides a full drill-down beyond the inline flow view to surface trends and anomalies. ## Configurable health status Today, a stage turns red when a technical signal fires. But a business flow can be broken for business reasons too — and the two don't always move together. The updated version of Pathpoint now lets you configure what makes a stage red: a technical condition like high latency on the Add to Cart service, or a business condition like cart abandonment crossing 50%. At the flow level, you can similarly configure overall flow health to reflect a flow-level KPI threshold rather than just a rollup of stage health. [Learn more about the updated version of Pathpoint](https://docs.newrelic.com/docs/pathpoint/get-started-pathpoint/), or find it under **All Capabilities** in the New Relic platform.52:Tdb4,Linux and Windows host support for Agent Control and Fleet Control reaches General Availability today, matching the GA support for Kubernetes that shipped in September 2025. New Relic Control now gives you one observability control plane across Kubernetes, Linux, and Windows hosts, so your entire fleet is managed the same way no matter where it runs. ## Host-based fleets for Linux and Windows Linux and Windows hosts now join Kubernetes clusters as first-class fleet types in Fleet Control and supported platforms for Agent Control. Group hosts into fleets by environment, application, or business unit, and apply the same RBAC, configuration templates, and deployment strategies you already use for Kubernetes, regardless of operating system. Roll out a change to thousands of hosts as easily as to a single cluster. ## Configuration approval governance Fleet Control now gives you governance over every agent configuration change before it reaches your fleet. An approval workflow lets you decide exactly how many people must approve a config change and set different rules for different agent types, so nothing ships without the review your team requires. Every approval, and every deployment it authorizes, is captured in Fleet Control's audit log, so you can always answer who changed what and when. ## Remote agent upgrades now available on hosts Agent Control can now remotely update itself and its managed agents on Linux and Windows hosts, the same way it already does on Kubernetes. Deploy a configuration change through Fleet Control, and any agent that needs an update, including Agent Control itself, can be upgraded as part of that deployment. Keeping your fleet current stops being a separate project and becomes a property of using Fleet Control. ## Initial wave of on-host integrations On-host integrations move from Public Preview to General Availability alongside the New Relic infrastructure agent, including Flex, Redis, NGINX, MySQL, PostgreSQL, Memcached, and Apache. All are fully supported on both Linux and Windows. This is the first wave of several planned batches, with more integrations rolling out in upcoming releases. ## Agent version intelligence, right where you deploy When you deploy or update an agent from Fleet Control, the deployment page now shows richer detail on the agent type itself, including its version history, feature notes, bug fixes, security notes, breaking changes, and end-of-life dates, all pulled live from the associated version. Make your upgrade decision from the same screen where you're already configuring the deployment, instead of cross-referencing external release notes. ## More secret and value provider support Agent Control now pulls configuration values from an even wider range of sources, including HashiCorp Vault, Kubernetes Secrets, Kubernetes ConfigMaps, local files, and environment variables. Wherever a value already lives, your agent configuration authored in Fleet Control can reference it directly, so you're not stuck duplicating settings or relocating secrets just to get Agent Control running. ## Get started - [New Relic Control](https://docs.newrelic.com/docs/new-relic-control/getting-started/) - [Agent Control overview](https://docs.newrelic.com/docs/new-relic-control/agent-control/overview/) - [Supported agent types](https://docs.newrelic.com/docs/new-relic-control/agent-control/agent-types/) - [Overview of Fleet Control](https://docs.newrelic.com/docs/new-relic-control/fleet-control/overview/)53:T9fb,New Relic dashboards now support a `{{selfEntity}}` template variable that resolves to the dashboard's own entity GUID, wherever you reference it in that dashboard's configuration. ## What you can do with {{selfEntity}} Previously, making a widget reference its own dashboard — for example, to keep facet linking pointed at the right place — meant hardcoding that dashboard's GUID. Duplicate the dashboard, and every hardcoded reference still pointed back at the original, breaking facet links and any other self-referencing configuration. Now you can drop `{{selfEntity}}` into any part of a widget's raw configuration, and New Relic resolves it to whichever dashboard the widget currently lives on: - **Facet linking**: Add `{{selfEntity}}` to `linkedEntityGuids` so a widget always links back to its own dashboard, not the dashboard you copied it from. - **Widget names**: Reference `{{selfEntity}}` in a widget's title. - **NRQL queries**: Use `{{selfEntity}}` inside a query, for example to filter results to the dashboard's own entity. - **Markdown widgets**: Reference `{{selfEntity}}` inside markdown widget text. - **Any other rawConfiguration field**: Use `{{selfEntity}}` in any field where you'd otherwise hardcode a dashboard GUID. ## How to get started How you adopt `{{selfEntity}}` depends on how the dashboard is managed: - **Facet linking on existing dashboards**: In the UI, disable facet linking on the widget and apply the change, then re-enable it. This replaces the hardcoded dashboard GUID with `{{selfEntity}}`. - **Facet linking on new dashboards**: Rely on the default behavior — New Relic applies `{{selfEntity}}` automatically, with no manual step needed. - **Terraform or JSON-defined dashboards**: Remove any hardcoded GUIDs and replace them with `{{selfEntity}}`, for example: ```json "widgets": [ { "id": "XXXXXXXX", "title": "Latest versions", "layout": { "column": 1, "row": 1, "width": 4, "height": 5 }, "visualization": { "id": "viz.table" }, "rawConfiguration": { "facet": { "showOtherSeries": false }, "linkedEntityGuids": [ "{{selfEntity}}" ], "nrqlQueries": [ { "accountIds": [ XXXXXXX, YYYYYYY ], "query": "YOUR_QUERY" } ], } } ] ``` To learn more, see [Filter New Relic dashboards by facets](https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/filter-new-relic-one-dashboards-facets/)54:T4e1,Complex traces that span dozens of services can make trace maps unreadable when every node is rendered at once. Services causing latency or errors get buried in visual noise, which makes troubleshooting harder. We've unified the trace map experience and added clustering logic to limit how many nodes the map displays at once. ## What's new - **Focus on high-importance services**: Key services stay visible in the trace view automatically. - **Long-tail collapse**: Low-importance services collapse into a cluster node that shows the number of hidden services. - **Dynamic ranking**: New Relic ranks and prioritizes services by their latency and error rate impact. ## Why it matters - **Faster mean time to identify (MTTI)**: Find bottlenecks and failing services without filtering through clutter. - **Consistent experience**: Trace maps now match the map experience used across the rest of New Relic. ## How to get started The new trace map opens from a trace: 1. Go to **Traces**. 2. In the **Trace groups** table, select a trace group. A drawer opens with all traces in that group. 3. Select a trace to see the new map. New Relic displays the new trace map by default. You can switch back to the previous map experience if you need to.55:T41b,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. ![Multi-account (up to 30) toggle in the account dropdown](https://docs.newrelic.com/images/multi-account-query.webp "Multi-account (up to 30)") As you grow your applications, more accounts are sometimes required to segment your data into different application/business segments. However, this data still relates to one another and sometimes needs to be queried all at once. Whether you are aggregating a summary across multiple accounts to present to your executive team, or researching an incident that affected multiple parts of your application, querying across many accounts is crucial. Learn how to query multiple accounts in the link below: [API - multi-account formatting](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-dashboards/#cross-account-dashboard)56:T4d2,A single threshold breach does not always provide enough context to determine whether an issue requires attention. With New Relic Compound Alerts, teams can combine up to five existing alert conditions and use AND and OR logic to define the specific combination that triggers a compound alert event. For example, rather than opening an alert event whenever application latency increases, a team can require both elevated latency and an increase in error rate. This helps teams avoid reacting to isolated threshold breaches and focus on combinations of conditions that more accurately represent the situations they want to investigate. Compound Alerts gives teams greater control over their alerting strategies while improving the quality of the signals that initiate investigation and response. As part of the Detect stage of New Relic Autonomous Operations, it helps teams identify when related conditions collectively warrant attention, while keeping customers in control of the conditions and logic used. New Relic Compound Alerts are available from September 22nd onwards. Learn more about [New Relic Compound Alerts](https://docs.newrelic.com/docs/alerts/create-alert/create-alert-condition/compound-alerts/compound-alerts/).57:T9fb,New Relic dashboards now support a `{{selfEntity}}` template variable that resolves to the dashboard's own entity GUID, wherever you reference it in that dashboard's configuration. ## What you can do with {{selfEntity}} Previously, making a widget reference its own dashboard — for example, to keep facet linking pointed at the right place — meant hardcoding that dashboard's GUID. Duplicate the dashboard, and every hardcoded reference still pointed back at the original, breaking facet links and any other self-referencing configuration. Now you can drop `{{selfEntity}}` into any part of a widget's raw configuration, and New Relic resolves it to whichever dashboard the widget currently lives on: - **Facet linking**: Add `{{selfEntity}}` to `linkedEntityGuids` so a widget always links back to its own dashboard, not the dashboard you copied it from. - **Widget names**: Reference `{{selfEntity}}` in a widget's title. - **NRQL queries**: Use `{{selfEntity}}` inside a query, for example to filter results to the dashboard's own entity. - **Markdown widgets**: Reference `{{selfEntity}}` inside markdown widget text. - **Any other rawConfiguration field**: Use `{{selfEntity}}` in any field where you'd otherwise hardcode a dashboard GUID. ## How to get started How you adopt `{{selfEntity}}` depends on how the dashboard is managed: - **Facet linking on existing dashboards**: In the UI, disable facet linking on the widget and apply the change, then re-enable it. This replaces the hardcoded dashboard GUID with `{{selfEntity}}`. - **Facet linking on new dashboards**: Rely on the default behavior — New Relic applies `{{selfEntity}}` automatically, with no manual step needed. - **Terraform or JSON-defined dashboards**: Remove any hardcoded GUIDs and replace them with `{{selfEntity}}`, for example: ```json "widgets": [ { "id": "XXXXXXXX", "title": "Latest versions", "layout": { "column": 1, "row": 1, "width": 4, "height": 5 }, "visualization": { "id": "viz.table" }, "rawConfiguration": { "facet": { "showOtherSeries": false }, "linkedEntityGuids": [ "{{selfEntity}}" ], "nrqlQueries": [ { "accountIds": [ XXXXXXX, YYYYYYY ], "query": "YOUR_QUERY" } ], } } ] ``` To learn more, see [Filter New Relic dashboards by facets](https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/filter-new-relic-one-dashboards-facets/)58:Td2c,New Relic Ground Truth is here, giving engineering teams a trusted operational intelligence layer for enterprise AI. As organizations bring AI assistants and agents into operational workflows, the challenge is no longer simply connecting AI to more data. It is giving AI access to the right operational context, with the governance and controls enterprises require. Ground Truth makes New Relic’s telemetry, entity relationships, system context, and operational knowledge accessible to AI tools and agents through MCP. Instead of requiring teams to assemble context across disconnected sources, Ground Truth helps AI understand what is happening across your environment and provides the evidence behind that understanding. ## What you can do with Ground Truth - **Connect AI tools and agents to New Relic operational intelligence:** Give approved AI systems access to relevant telemetry and operational context through MCP. - **Provide richer context about your environment:** Help AI understand services, entities, dependencies, changes, and related telemetry rather than reasoning from isolated signals. - **Ground AI responses in observable evidence:** Enable AI systems to use current New Relic data and context so teams can evaluate findings against the underlying telemetry. - **Control how operational context is accessed:** Use New Relic permissions and administrative controls to govern which capabilities and connections are available across your organization. - **Extend operational intelligence beyond the New Relic UI:** Bring trusted New Relic context into the AI tools and workflows where your teams already work. ## Built for AI that needs more than data AI becomes more useful in operations when it understands the environment it is reasoning about. Ground Truth brings together telemetry and operational context so AI tools and agents can work from a richer understanding of your systems rather than interpreting individual signals in isolation. That makes Ground Truth more than an integration point. It establishes a foundation for making trusted New Relic operational intelligence available to New Relic and third-party AI experiences. ## Connect through MCP Ground Truth includes MCP server capabilities that provide a standards-based way for compatible AI tools and agents to access New Relic operational intelligence Organizations that participated in the New Relic MCP Server Public Preview can continue using those capabilities as part of Ground Truth, with administrative controls for managing access and available connections. Organizations new to Ground Truth can enable its MCP server capabilities through Feature Control Manager to start connecting compatible AI tools. This means existing Preview customers retain a familiar way to connect their AI tools, while new customers gain a straightforward path to begin using Ground Truth. ## Govern access to operational intelligence Ground Truth is designed for enterprise environments where access to operational data must remain controlled. New Relic permissions and Feature Control Manager help administrators determine which MCP capabilities and connections are available to their organizations, while maintaining control over how AI systems access New Relic context. Learn more about [Ground Truth](https://docs.newrelic.com/docs/agentic-ai/mcp/overview/), or get started today.59:T565,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. With New Relic Lens, you can easily connect your observability data directly to your business outcomes and transform that data into actionable insights, all without paying for extra data ingestion. New Relic Lens allows you to connect and query multiple external data sources like Snowflake, Iceberg, Google Sheets, and many more using SQL – all from within the New Relic UI. Users can combine, analyze and correlate telemetry and non-telemetry (business) data using sophisticated cross-database joins without ingesting the external data. You can run a Lens query in the Query Builder, within the new Notebooks feature, or saved within a Dashboard. Whether you are a DevOps engineer wanting to combine data from different databases, or a Product Manager looking to display revenue data alongside usage for your executive suite, or a comms manager trying to find the correct person to contact, New Relic Lens can help you query data where it lives and enhance your Observability experience. **Find out more**: - [Learn more](https://docs.newrelic.com/docs/new-relic-lens/overview/) - [Blog](https://newrelic.com/blog/news/streamline-data-discovery-and-analysis)5a:T6f6,Grouping and column options aren't new to Catalogs — we've always offered a curated set of the most relevant options out of the box, so you get a high-signal view without the noise. Now, you can go further: **group entities and add columns using any tag**, whether it's a New Relic-defined tag or a custom tag your team already relies on, then **reorder them** to match your workflow—with your custom layout **saved automatically** for your next visit. ## Key benefits to your workflow - **Curated by default, extensible when you need it:** Start with the high-signal options Catalogs surfaces out of the box, then layer in any tag — New Relic-defined or custom — for the context specific to your team. - **Surface the metadata that matters most:** Any tag can become now a column and/or a group. Combine them together — for example, group by team while adding an environment or cost-center column — for much better visibility into how your systems actually break down. - **A layout that fits your workflow, not the other way around:** Reorder columns so the information you check first is always the information you see first. ## How to get started 1. Navigate to your [Applications, Infrastructure, or Repositories Catalog](https://one.newrelic.com/catalogs/). 2. Open the **Group By** and **Column** picker dropdowns in the top right corner of the Catalogs table to see and search every tag available in your account, alongside the curated options you already know. 3. Click and drag column headers to reorder your view. 4. And remember, your layout is remembered, so it's exactly how you left it next time you come back. To learn more, check out the [Catalogs documentation](https://docs.newrelic.com/docs/service-architecture-intelligence/catalogs/catalogs/).5b:T5d6,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. ## What you get - **Full LLM visibility without an agent** — Set two environment variables, add the GenAI instrumentation package for your framework, and your spans start flowing into AI monitoring. No new agent to install. - **Support for popular frameworks** — Works with the OpenTelemetry GenAI instrumentation packages for OpenAI, Anthropic, LangChain, and AWS Bedrock. Any other language or framework with OTel GenAI instrumentation works the same way. - **Privacy-first content capture** — Prompt and completion content capture is off by default. Opt in explicitly when you're ready, and use drop filters or attribute-level obfuscation to protect sensitive data before it reaches New Relic. - **Full trace context** — LLM calls appear as spans within your existing distributed traces, so you can correlate model latency and errors with the rest of your service in a single view. ## Get started Set your two OTLP exporter environment variables, add the GenAI instrumentation package for your framework, and send a small amount of traffic. Within a few minutes your service appears in AI monitoring. See the [OpenTelemetry AI monitoring documentation](https://docs.newrelic.com/docs/ai-monitoring/opentelemetry-ai-monitoring/) for the full setup.47:["$","$L4a",null,{"orgSlug":"newrelic","sourceSlug":"newrelic-whats-new","initialReleases":[{"id":"rel_AtbrXpz0ZYaaFpznwe9sH","title":"Oracle Cloud Infrastructure integration is now generally available","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-27-oci-ga","publishedAt":"2026-10-27T00:00:00.000Z","fetchedAt":"2026-10-27T16:06:48.767Z","titleGenerated":"New Relic OCI integration reaches GA with native metrics and logs ingestion","titleShort":"OCI metrics and logs now flow into New Relic","importance":3,"content":"$4b","summary":"New Relic's OCI integration is generally available, adding out-of-the-box ingestion for metrics and logs from OCI Compute, Storage, Database, and Network services. OCI telemetry now sits alongside AWS, Azure, and GCP data in one platform for cross-cloud troubleshooting.","media":[],"bodyHtml":"

New Relic's OCI integration is generally available, adding out-of-the-box ingestion for metrics and logs from OCI Compute, Storage, Database, and Network services. OCI telemetry now sits alongside AWS, Azure, and GCP data in one platform for cross-cloud troubleshooting.

"},{"id":"rel_OyDqkbRXEfleP6u0dZ26w","title":"NRQL Macros is now generally available","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-26-nrql-macros-ga","publishedAt":"2026-10-26T00:00:00.000Z","fetchedAt":"2026-10-26T20:06:45.943Z","titleGenerated":"New Relic NRQL Macros reaches general availability","titleShort":"NRQL Macros now generally available","importance":3,"content":"We're excited to announce that NRQL Macros is now generally available. Macros allows you to save a NRQL expression as a reusable, named shortcut. This can be used to simplify your queries, set an alias, create a single source of truth, and many more applications.\n\nExample macro: `$podnameAlias = (podName OR pod_name OR pod.name)`\n\nMacro in action: `SELECT count(*) FROM Log FACET $podnameAlias`\n\nA macro can be a small alias like above, or a large WHERE clause taking up space. Best of all, you can change this one macro and it will update every query it is a part of. This can particularly come in handy if a handful of widgets on a dashboard need to be updated all at once.\n\nMacros can be created/edited in the **Administration > NRQL Macro** UI, or via our API.\n\nWe're excited to see all the different ways you will use macros to optimize/simplify your NRQL!\n\nLearn more about [NRQL Macros](https://docs.newrelic.com/docs/nrql/nrql-macros/nrql-macros-overview).","summary":"NRQL Macros is generally available, letting users save a NRQL expression as a reusable named shortcut that can be referenced in queries and updated in one place across every query that uses it. Macros are created and edited in Administration > NRQL Macro or via the API.","media":[],"bodyHtml":"

NRQL Macros is generally available, letting users save a NRQL expression as a reusable named shortcut that can be referenced in queries and updated in one place across every query that uses it. Macros are created and edited in Administration > NRQL Macro or via the API.

"},{"id":"rel_YghUITUll_I2qDLy60s6I","title":"Performance Risks Inbox is now generally available","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-08-performance-risks-inbox","publishedAt":"2026-10-08T00:00:00.000Z","fetchedAt":"2026-10-08T16:05:43.491Z","titleGenerated":"New Relic Performance Risks Inbox reaches GA with account-level overview and AI insights","titleShort":"Performance Risks Inbox GA; AI-generated insights for risk groups","importance":3,"content":"$4c","summary":"Performance Risks Inbox is now generally available, adding an account-level overview page, support in Standard and Intelligent Workloads, AI-generated insights that summarize likely root causes for a risk group, and MCP server support. It surfaces anti-patterns such as N+1 queries and inefficient database calls in APM and Browser entity views, Triage Inbox, and Workloads.","media":[],"bodyHtml":"

Performance Risks Inbox is now generally available, adding an account-level overview page, support in Standard and Intelligent Workloads, AI-generated insights that summarize likely root causes for a risk group, and MCP server support. It surfaces anti-patterns such as N+1 queries and inefficient database calls in APM and Browser entity views, Triage Inbox, and Workloads.

"},{"id":"rel_LEPgxEe1SbdLBJ-byV3p-","title":"Top-level navigation label 'Errors Inbox' is now 'Triage Inbox'","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-08-triage-inbox-nav-label","publishedAt":"2026-10-08T00:00:00.000Z","fetchedAt":"2026-10-08T12:05:43.306Z","titleGenerated":"New Relic renames main navigation label Errors Inbox to Triage Inbox","titleShort":"Errors Inbox nav label now Triage Inbox","importance":1,"content":"**Errors Inbox** in New Relic's main navigation is now **Triage Inbox (Errors Inbox)**. Open it and you'll find the same two places you already use: **Errors Inbox** and **Performance Risks Inbox**.\n\nThis is a change to the label for the main navigation entry and nothing else. There's no new page and no new feature to turn on. Errors Inbox and Performance Risks Inbox both work exactly as they did before, Errors Inbox inside your entity views is unchanged, and there's no change to pricing or billing.\n\n![Triage Inbox (Errors Inbox) in the main navigation](https://docs.newrelic.com/images/triage-inbox-nav-label.gif \"Triage Inbox (Errors Inbox) in the main navigation\")\n\nWe're keeping **(Errors Inbox)** next to the new name **Triage Inbox** for a few more months so the entry stays easy to recognize.","summary":"New Relic's top-level navigation entry Errors Inbox is now labeled Triage Inbox (Errors Inbox), with the old name kept in parentheses for a few more months. Errors Inbox and Performance Risks Inbox pages are unchanged, as are entity-view Errors Inbox and pricing.","media":[{"type":"gif","url":"https://docs.newrelic.com/images/triage-inbox-nav-label.gif","alt":"Triage Inbox (Errors Inbox) in the main navigation","r2Url":"https://media.releases.sh/releases/6312e8fb2aa7c517bd896d91438a3102d2167b0a04091527f7719bad40c70fb9.mp4"}],"bodyHtml":"

New Relic's top-level navigation entry Errors Inbox is now labeled Triage Inbox (Errors Inbox), with the old name kept in parentheses for a few more months. Errors Inbox and Performance Risks Inbox pages are unchanged, as are entity-view Errors Inbox and pricing.

"},{"id":"rel_1Oq-b8ZOLfsWhaYbPAC_-","title":"Updates to Intelligent Workloads and Standard Workloads","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-08-Workloads-GA","publishedAt":"2026-10-08T00:00:00.000Z","fetchedAt":"2026-10-08T20:05:43.815Z","titleGenerated":"New Relic Workloads GA adds bulk creation, exclude filters, and alert policy health","titleShort":"Intelligent Workloads GA; bulk create and exclude filters added","importance":4,"content":"$4d","summary":"Intelligent Workloads is now generally available, with bulk creation that surfaces candidate transactions by processing time, latency, or error rates, and exclude filters that prune unowned microservices, third-party APIs, or irrelevant pipeline branches from the dependency graph. Standard Workloads gains a context-rich summary page and support for custom alert policies and conditions for health configuration.","media":[],"bodyHtml":"

Intelligent Workloads is now generally available, with bulk creation that surfaces candidate transactions by processing time, latency, or error rates, and exclude filters that prune unowned microservices, third-party APIs, or irrelevant pipeline branches from the dependency graph. Standard Workloads gains a context-rich summary page and support for custom alert policies and conditions for health configuration.

"},{"id":"rel_WMmy3fD8Ow7THDDWckKUR","title":"Manage New Relic Notebooks with Terraform","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-06-notebooks-terraform","publishedAt":"2026-10-06T00:00:00.000Z","fetchedAt":"2026-10-06T20:05:37.095Z","titleGenerated":"New Relic Notebooks can now be managed with Terraform","titleShort":"Notebooks now manageable as Terraform resource","importance":3,"content":"$4e","summary":"New Relic Notebooks can be defined, provisioned, and managed through a native Terraform resource with full CRUD, enabling version control, pull request review, and deployment alongside other infrastructure code. Access management via user permissions and a Blob Storage API for automated notebook workflows and AI agent integrations are also available.","media":[],"bodyHtml":"

New Relic Notebooks can be defined, provisioned, and managed through a native Terraform resource with full CRUD, enabling version control, pull request review, and deployment alongside other infrastructure code. Access management via user permissions and a Blob Storage API for automated notebook workflows and AI agent integrations are also available.

"},{"id":"rel_hEemiup_QSmCn4bM197wz","title":"Scheduled Search and Reporting is now generally available","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/10/whats-new-10-05-scheduled-search-reporting-ga","publishedAt":"2026-10-05T00:00:00.000Z","fetchedAt":"2026-10-05T16:05:34.386Z","titleGenerated":"New Relic makes Scheduled Search and Reporting generally available","titleShort":"Scheduled Search and Reporting now GA","importance":4,"content":"$4f","summary":"Scheduled Search and Reporting runs any NRQL query automatically on an hourly, daily, weekly, or custom cadence and delivers results to your inbox. Notification Conditions trigger delivery only when the query's result count meets a defined threshold.","media":[],"bodyHtml":"

Scheduled Search and Reporting runs any NRQL query automatically on an hourly, daily, weekly, or custom cadence and delivers results to your inbox. Notification Conditions trigger delivery only when the query's result count meets a defined threshold.

"},{"id":"rel_d8mkqxu5SVcTt4L1VsSpn","title":"Place pipeline processors anywhere you need them with Pipeline Control","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-30-pipeline-control-processors","publishedAt":"2026-09-30T00:00:00.000Z","fetchedAt":"2026-09-30T16:04:38.900Z","titleGenerated":"New Relic Pipeline Control lets processors be placed anywhere in a pipeline","titleShort":"Pipeline processors now go anywhere in the chain","importance":3,"content":"$50","summary":"Sample Rate, Filter, and Transform processors can now be added, stacked, reordered, or deleted at any point in a Pipeline Control pipeline, replacing the previous fixed one-of-each layout. Filter and Transform rules are backed by OTTL statements with recipes and payload preview, and changes are staged as drafts before deployment.","media":[],"bodyHtml":"

Sample Rate, Filter, and Transform processors can now be added, stacked, reordered, or deleted at any point in a Pipeline Control pipeline, replacing the previous fixed one-of-each layout. Filter and Transform rules are backed by OTTL statements with recipes and payload preview, and changes are staged as drafts before deployment.

"},{"id":"rel_69EvxQhFRUq3zOO2VEfLL","title":"The updated version of Pathpoint is now available in Public Preview","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-30-pathpoint-2-0","publishedAt":"2026-09-30T00:00:00.000Z","fetchedAt":"2026-09-30T20:04:39.366Z","titleGenerated":"New Relic Pathpoint 2.0 enters Public Preview with Terraform and NerdGraph API","titleShort":"Pathpoint 2.0 preview adds Terraform; health status configurable","importance":3,"content":"$51","summary":"The updated version of New Relic Pathpoint is available in Public Preview, adding a NerdGraph API and Terraform provider so Pathpoint flows can be created, versioned, and deployed through CI/CD pipelines, with existing generally available Pathpoint users able to export their configuration as Terraform. KPIs now surface flow-level and stage-level business metrics like orders placed, cart abandonment, and conversion rate, and stages can be configured to turn red on a business condition such as cart abandonment crossing 50%.","media":[],"bodyHtml":"

The updated version of New Relic Pathpoint is available in Public Preview, adding a NerdGraph API and Terraform provider so Pathpoint flows can be created, versioned, and deployed through CI/CD pipelines, with existing generally available Pathpoint users able to export their configuration as Terraform. KPIs now surface flow-level and stage-level business metrics like orders placed, cart abandonment, and conversion rate, and stages can be configured to turn red on a business condition such as cart abandonment crossing 50%.

"},{"id":"rel_aTb42XifZhsAIgLHupvaZ","title":"New Relic Control host-based fleets are now generally available","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-29-host-support-ga","publishedAt":"2026-09-29T00:00:00.000Z","fetchedAt":"2026-09-30T16:04:38.900Z","titleGenerated":"New Relic Control host-based fleets for Linux and Windows reach GA","titleShort":"Host fleets GA on Linux and Windows","importance":4,"content":"$52","summary":"Linux and Windows host support for Agent Control and Fleet Control is generally available, making hosts first-class fleet types alongside Kubernetes. Also new: a config-change approval workflow with audit logging, remote agent and self upgrades on hosts, GA of on-host integrations including Flex, Redis, NGINX, MySQL, PostgreSQL, Memcached, and Apache, and expanded value providers such as HashiCorp Vault, Kubernetes Secrets, and ConfigMaps.","media":[],"bodyHtml":"

Linux and Windows host support for Agent Control and Fleet Control is generally available, making hosts first-class fleet types alongside Kubernetes. Also new: a config-change approval workflow with audit logging, remote agent and self upgrades on hosts, GA of on-host integrations including Flex, Redis, NGINX, MySQL, PostgreSQL, Memcached, and Apache, and expanded value providers such as HashiCorp Vault, Kubernetes Secrets, and ConfigMaps.

"},{"id":"rel_3XaoQa_T8y-mUvD8LLUem","title":"Reference the current dashboard from anywhere with {{selfEntity}}","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-29-selfentity-dashboard-variable","publishedAt":"2026-09-29T00:00:00.000Z","fetchedAt":"2026-09-29T16:04:34.563Z","titleGenerated":"New Relic dashboards add {{selfEntity}} variable to replace hardcoded GUIDs","titleShort":"{{selfEntity}} replaces hardcoded dashboard GUIDs","importance":3,"content":"$53","summary":"Dashboards now support a {{selfEntity}} template variable that resolves to the dashboard's own entity GUID, usable in linkedEntityGuids, widget titles, NRQL queries, markdown widgets, and any other rawConfiguration field. Terraform or JSON-defined dashboards must replace hardcoded GUIDs with {{selfEntity}}, while existing dashboards can swap facet-linking GUIDs by toggling the setting off and on.","media":[],"bodyHtml":"

Dashboards now support a {{selfEntity}} template variable that resolves to the dashboard's own entity GUID, usable in linkedEntityGuids, widget titles, NRQL queries, markdown widgets, and any other rawConfiguration field. Terraform or JSON-defined dashboards must replace hardcoded GUIDs with {{selfEntity}}, while existing dashboards can swap facet-linking GUIDs by toggling the setting off and on.

"},{"id":"rel_9kCTa3I6IqsgFtGXGcKei","title":"A new trace map experience with intelligent clustering","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-28-trace-map-clustering","publishedAt":"2026-09-28T00:00:00.000Z","fetchedAt":"2026-09-30T16:04:38.900Z","titleGenerated":"New Relic adds intelligent clustering to unified trace map experience","titleShort":"Trace maps cluster low-importance services automatically","importance":3,"content":"$54","summary":"Trace maps now use clustering logic to limit how many nodes display at once: high-importance services stay visible, low-importance ones collapse into a cluster node showing the count of hidden services, and services are ranked by latency and error rate impact. The new map is the default and the previous experience remains available to switch back to.","media":[],"bodyHtml":"

Trace maps now use clustering logic to limit how many nodes display at once: high-importance services stay visible, low-importance ones collapse into a cluster node showing the count of hidden services, and services are ranked by latency and error rate impact. The new map is the default and the previous experience remains available to switch back to.

"},{"id":"rel_8Xkm_rmslxgUOTXV1l--C","title":"Session replay now has its own billing category","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-28-session-replay-billing-category","publishedAt":"2026-09-28T00:00:00.000Z","fetchedAt":"2026-09-29T16:04:34.563Z","titleGenerated":"New Relic splits session replay into its own billing category","titleShort":"Session replay gets its own billing category","importance":3,"content":"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.\n\nThis is a reporting change only: your session replay functionality, pricing, and total data ingested are unaffected. If you use NRQL to query usage data, for example faceting or filtering on `usage.metric` from `NrIngestedBytes`, update your queries to include the new categories: `BrowserSessionReplay` and `MobileSessionReplay`.\n\nLearn more about [data ingestion sources](https://docs.newrelic.com/docs/data-apis/manage-data/manage-data-coming-new-relic/#sources-list).","summary":"Session replay data for Browser and Mobile is now reported under its own billing category in Data ingestion and usage, instead of browser events and mobile events. NRQL queries that facet or filter on usage.metric from NrIngestedBytes must be updated to include the new BrowserSessionReplay and MobileSessionReplay categories.","media":[],"bodyHtml":"

Session replay data for Browser and Mobile is now reported under its own billing category in Data ingestion and usage, instead of browser events and mobile events. NRQL queries that facet or filter on usage.metric from NrIngestedBytes must be updated to include the new BrowserSessionReplay and MobileSessionReplay categories.

"},{"id":"rel_U48QxeQ9IoO8jHfSsZSTi","title":"Now query up to 30 New Relic accounts at once!","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-22-cross-account-query-limit-30","publishedAt":"2026-09-22T00:00:00.000Z","fetchedAt":"2026-09-22T20:04:03.930Z","titleGenerated":"New Relic raises cross-account query limit from 5 to 30 accounts","titleShort":"Cross-account query limit rises from 5 to 30","importance":3,"content":"$55","summary":"The maximum number of New Relic accounts that can be queried at once increases from 5 to 30, available through the \"Multi-account (up to 30)\" option in the account dropdown or via the API.","media":[{"type":"image","url":"https://docs.newrelic.com/images/multi-account-query.webp","alt":"Multi-account (up to 30) toggle in the account dropdown","r2Url":"https://media.releases.sh/releases/fed73d5c30e2920a1f957f390d5cbbf089997d6577fcab9fbdf550fc6a671ea3.webp"}],"bodyHtml":"

The maximum number of New Relic accounts that can be queried at once increases from 5 to 30, available through the \"Multi-account (up to 30)\" option in the account dropdown or via the API.

"},{"id":"rel_ADmB_x8Ul9SLChRSf4Uki","title":"New Relic Compound Alerts brings multiple conditions together for more precise alerting","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-22-compound-alerts","publishedAt":"2026-09-22T00:00:00.000Z","fetchedAt":"2026-09-23T16:04:06.521Z","titleGenerated":"New Relic launches Compound Alerts with AND/OR logic across up to five conditions","titleShort":"Compound Alerts combine up to five conditions with AND/OR logic","importance":3,"content":"$56","summary":"Compound Alerts lets teams combine up to five existing alert conditions with AND and OR logic to define which combination triggers a compound alert event, such as requiring elevated latency and a higher error rate together. Available from September 22 as part of the Detect stage of New Relic Autonomous Operations.","media":[],"bodyHtml":"

Compound Alerts lets teams combine up to five existing alert conditions with AND and OR logic to define which combination triggers a compound alert event, such as requiring elevated latency and a higher error rate together. Available from September 22 as part of the Detect stage of New Relic Autonomous Operations.

"},{"id":"rel_G_6e8_NFWtWwa8rMD3E1b","title":"Reference the current dashboard from anywhere with {{selfEntity}}","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-16-selfentity-dashboard-variable","publishedAt":"2026-09-16T00:00:00.000Z","fetchedAt":"2026-09-16T16:01:52.426Z","titleGenerated":"New Relic adds {{selfEntity}} dashboard variable for self-referencing config","titleShort":"{{selfEntity}} resolves dashboards to own GUID","importance":3,"content":"$57","summary":"A {{selfEntity}} template variable now resolves to the dashboard's own entity GUID anywhere in its raw configuration, so duplicated dashboards no longer point facet links and other self-references back at the original. Existing dashboards need facet linking disabled and re-enabled to swap in the variable, while new dashboards get it by default.","media":[],"bodyHtml":"

A {{selfEntity}} template variable now resolves to the dashboard's own entity GUID anywhere in its raw configuration, so duplicated dashboards no longer point facet links and other self-references back at the original. Existing dashboards need facet linking disabled and re-enabled to swap in the variable, while new dashboards get it by default.

"},{"id":"rel_6LzcwppQyT-8qeTS5GLlz","title":"Connect AI to trusted operational context with New Relic Ground Truth","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-15-ground-truth","publishedAt":"2026-09-15T00:00:00.000Z","fetchedAt":"2026-09-15T16:01:46.429Z","titleGenerated":"New Relic launches Ground Truth to connect AI agents to operational telemetry via MCP","titleShort":"Ground Truth exposes New Relic telemetry to AI agents via MCP","importance":4,"content":"$58","summary":"New Relic Ground Truth gives approved AI tools and agents access to telemetry, entity relationships, system context, and operational knowledge through MCP, governed by New Relic permissions and Feature Control Manager. Organizations in the MCP Server Public Preview keep their existing capabilities, and new organizations can enable MCP server capabilities through Feature Control Manager.","media":[],"bodyHtml":"

New Relic Ground Truth gives approved AI tools and agents access to telemetry, entity relationships, system context, and operational knowledge through MCP, governed by New Relic permissions and Feature Control Manager. Organizations in the MCP Server Public Preview keep their existing capabilities, and new organizations can enable MCP server capabilities through Feature Control Manager.

"},{"id":"rel_22a6yq-tn58UB53pa-DEw","title":"New Relic Lens is now generally available","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-15-nr-lens-ga","publishedAt":"2026-09-15T00:00:00.000Z","fetchedAt":"2026-09-15T16:01:46.429Z","titleGenerated":"New Relic Lens reaches GA with SQL federation across external data sources","titleShort":"New Relic Lens GA: SQL federation without extra ingestion","importance":4,"content":"$59","summary":"New Relic Lens is now generally available, letting users connect and query external data sources such as Snowflake, Iceberg, and Google Sheets with SQL from the New Relic UI, including cross-database joins without ingesting the external data. Lens queries can run in Query Builder, the new Notebooks feature, or saved in a Dashboard.","media":[],"bodyHtml":"

New Relic Lens is now generally available, letting users connect and query external data sources such as Snowflake, Iceberg, and Google Sheets with SQL from the New Relic UI, including cross-database joins without ingesting the external data. Lens queries can run in Query Builder, the new Notebooks feature, or saved in a Dashboard.

"},{"id":"rel_v0To10nkl9UR3zHB8v9FV","title":"Tag-based grouping, custom columns, and column reordering in Catalogs","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/09/whats-new-09-07-catalogs-tag-grouping","publishedAt":"2026-09-07T00:00:00.000Z","fetchedAt":"2026-09-15T11:51:08.790Z","titleGenerated":null,"titleShort":null,"importance":null,"content":"$5a","summary":"","media":[],"bodyHtml":"

Grouping and column options aren't new to Catalogs — we've always offered a curated set of the most relevant options out of the box, so you get a high-signal view without the noise.

"},{"id":"rel_OUTcsR-7j8-DwF2ipggmm","title":"OpenTelemetry support for AI monitoring is now GA","version":null,"type":"feature","url":"https://docs.newrelic.com/whats-new/2026/08/whats-new-08-26-otel-ai-monitoring","publishedAt":"2026-08-31T00:00:00.000Z","fetchedAt":"2026-09-15T11:51:08.790Z","titleGenerated":null,"titleShort":null,"importance":null,"content":"$5b","summary":"","media":[],"bodyHtml":"

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.

"}],"initialCursor":"2026-08-31T00:00:00.000Z|2026-09-15T11:51:08.790Z|rel_OUTcsR-7j8-DwF2ipggmm","appStore":null,"video":null,"sourceName":"What's New"}] 48:[["$","$3e",null,{"fallback":null,"children":"$L5c"}],["$","$3e",null,{"fallback":null,"children":"$L5d"}]]

What's New

More from New Relic

From other products

More from New Relic

From other products