Safeguard Your Critical Operations with Unified, Intelligent Context

In complex environments, the gap between observability and actionable business context often widens. To close that gap, we're significantly expanding the power of the New Relic platform with five capabilities, now generally available.

These capabilities deliver unified intelligent observability that connects your code health directly to business outcomes, security posture, and engineering team ownership.

Safeguard Critical Revenue Paths

When outages hit revenue-generating systems, every second counts. But as applications become more complex, the flood of alerts from interconnected services overwhelms DevOps teams, slowing troubleshooting and increasing downtime.

The Challenge: A developer at a major e-commerce platform gets woken at 2:00 AM by alerts flooding in from the checkout service and multiple related services. Opening separate dashboards for each service, each in different browser tabs, they're drowning in top-down stack views with no unified picture of what's actually breaking the checkout flow. Revenue is bleeding while they hunt for the needle in the haystack.

Transaction 360 eliminates this fragmentation. It automatically aggregates relevant components (APM, Browser, Infrastructure), along with telemetry and crucial data like alerts and change trackers into a unified view. By combining transaction tracing and distributed tracing, Transaction 360 offers a complete, unsampled picture of issue-specific data, reducing MTTR by up to 5x.

Transaction 360 provides comprehensive visibility spanning days and weeks, with dynamic workload creation that automatically builds collections of entities for transactions experiencing issues. When that 2:00 AM alert hits, engineers see exactly which component in the transaction flow is causing the problem.

Embed Security and Compliance into Engineering

Security teams are drowning in alerts. According to CSA's State of Security Remediation report, 75% of organizations have security teams spending over 20% of their time performing manual tasks when addressing security alerts, and over half of the vulnerabilities addressed recur within a month of remediation.

The Challenge: A developer receives 50 security incident tickets, all marked "critical," all demanding immediate fixes across 10 services. With no prioritization and a high-priority feature launch deadline looming, the developer closes the tickets and gets back to coding. The business is now exposed to potential breach risk, but which of those 50 vulnerabilities actually pose material risk? No one knows.

Security RX shifts teams from reactive patching to proactive risk management. It integrates vulnerability prioritization directly into your observability platform, cutting the volume of vulnerabilities from code scanning tools by up to 97% with runtime verification. By combining threat intelligence with observability context, Security RX surfaces only the 3% of risks that really matter, giving DevOps up to 60% of their time back.

Entity and Relationship History provides a "time-travel" view of your infrastructure and services estate. Access historical entity and relationship data over a 30-day rolling period to instantly detect configuration drift, validate changes, and maintain audit trails for compliance.

The Challenge: During an audit, your team needs to prove that specific security configurations were in place three weeks ago when a compliance check occurred. Previously, this meant hunting through multiple systems, hoping someone documented the state. Now, Entity and Relationship History lets you query exactly what existed at that point in time, which hosts were running, what their configurations were, and how they related to other entities.

For regulated industries like banking or telco, Entity and Relationship History simplifies audits and troubleshooting by consolidating security and observability in the same platform.

Eliminate Silos and Drive Accountability

When incidents arise in microservice-based systems, coordination between teams often gets hindered by the complexity of determining dependencies and ownership of interdependent services.

The Challenge: A critical service is down at 4:00 AM. The on-call engineer knows it's not their service causing the issue, it's an issue owned by another team. Who? They start asking in Slack, check outdated spreadsheets, even schedule an emergency war room meeting while the outage continues. Thirty minutes are wasted just figuring out who to call.

Service Architecture Intelligence Teams embeds service ownership directly into the platform. During an incident, team information is immediately available in the Issues page, showing who owns the affected entities, their contact information, and even their on-call schedules.

Teams automatically generates a Teams Hub, a centralized space showing all entities your team owns, health status, important dashboards, documentation, runbooks, and workflows. By clarifying resource ownership and helping teams understand each other's governance, Service Architecture Intelligence Teams facilitates collaborative management of shared resources like databases and messaging queues, resolving incidents faster and improving efficiency.

Service Architecture Intelligence Scorecards measures and reports on goals, software quality, security posture, developer productivity, production readiness, and compliance status.

The Challenge: Your organization has many  microservices, and before every production launch, SREs manually meet with each service owner to walk through a lengthy production-readiness checklist (instrumentation, data security, API standards, database usage). It's not scalable and services slip through with gaps that cause downstream incidents.

With Scorecards, engineering leaders eliminate manual tracking and spreadsheets by defining standards like production readiness and development quality, then enforcing them automatically. Out-of-the-box scorecards can be quickly enabled and modified, while custom scorecards leverage NRQL rules to align with your engineering best practices. 

Executives get organization-wide snapshots of engineering performance across distributed teams. Team leads gain actionable insights to track progress and allocate resources effectively. 

Built-In Control for Flexible Adoption

We understand that adding powerful capabilities requires control. That’s why we are excited to introduce Feature Control Manager and Data Ingest Budgets. Take control of your observability costs and prioritize spend where it matters to your business. You decide exactly when to toggle these new capabilities ON or OFF at the org or account level.

Now generally available, Feature Control Manager gives admins centralized governance to toggle Transaction 360, Security RX, Service Architecture Intelligence Teams and Scorecards on or off at the organization or account level. You decide how and when to roll out these capabilities to your teams, ensuring you only consume what drives value for your business. 

Also generally available, Data Ingest Budgets enables you to create budgets specifically for data ingestion costs, set thresholds, and receive notifications when approaching limits. This gives you complete control over usage and ingestion.

Get Started

These capabilities are available now in the Advanced Compute Bundle. Whether you're protecting critical business transactions, embedding security into engineering workflows, or driving engineering excellence across distributed teams, New Relic delivers the unified, intelligent context you need to succeed.

Learn more:

• Transaction 360
• Security RX
• Service Architecture Intelligence Teams & Scorecards
• Entity and Relationship History
• Feature Control Manager

Contact us to discuss how these capabilities can transform your observability practice.