Reduce MTTR: Accelerate Cloud Incident Triage with New Relic Infrastructure 360

To support modern development, platform engineers must balance four critical pillars: velocity, reliability, cost, and security. As modern cloud environments grow more complex and scale at unprecedented speed, the traditional approach to infrastructure monitoring—simply providing metrics to view entity health—is no longer sufficient. Half of major production outages stem directly from untracked infrastructure changes. When an alert fires today, platform engineers and SREs don't just need to know that a host CPU or memory limit is breached; they need an immediate 360-degree view of downstream dependencies to evaluate customer business impact and prevent user-facing outages.

To solve this, the design point for Infrastructure 360 was deeply rooted in the concept of platform observability and layers. Instead of building a disjointed tool, Infrastructure 360 was designed to leverage focused aspects of the New Relic platform, providing progressive layers of advanced capabilities to meet everything from basic health checks to highly complex troubleshooting needs.

Imagine an automated deployment alters an Azure Application Gateway rule at 2:00 AM, triggering latency spikes across downstream Kubernetes microservices. Instead of SREs guessing which team's deploy broke the app, Infrastructure 360 immediately correlates the latency alert on the APM entity page to the exact line-item config difference on the gateway.

Infrastructure 360 offers users:

• End-to-End Visibility: Automatically maps complex dependencies across AWS, Azure, and multi-region Kubernetes estates to eliminate cloud blind spots and accelerate triage.
• Instant Configuration Context: Tracks configuration edits and leverages the Configuration Explorer for property-level analysis, directly correlating changes to performance drops.
• Foundational AI Readiness: Supplies precise topology maps and change context to power New Relic Autopilot with zero-maintenance reliability for automated remediation.

Progressive Diagnostic Depth: From Surface Health Alerts to Structural Root Causes

When a critical outage strikes, platform engineers need fast, definitive answers. Traditional infrastructure monitoring usually stops after telling you that a host is degrading or a CPU threshold has breached, leaving responders stranded when trying to uncover the broader system impact. Finding out why an anomaly occurred or what else is failing typically requires manual data-scavenging across disparate cloud consoles and dashboards.

Infrastructure 360 replaces this fragmented workflow with progressive diagnostic depth built directly into your daily workspace. Instead of forcing engineers to jump between disconnected tools, the platform systematically elevates your triage journey across three seamless stages:

1. Surface Health & Alert Context: Instantly validate baseline entity health, resource consumption, and active alert conditions across your multi-cloud footprint.
2. Automated Dependency & Blast Radius Mapping: Expand your view instantly beyond the isolated alert to see how the failing component connects to upstream application gateways, load balancers, and downstream microservices.
3. Configuration Change Impact Analysis: Surface exact, property-level configuration edits that occurred leading up to the anomaly, linking infrastructure changes directly to application performance drops.

By moving progressively from basic health checks to real-time structural context, Infrastructure 360 answers the critical operational questions—What is actually running? How are these components connected? What configuration change broke this service? This transforms reactive firefighting into a fast, deterministic triage workflow that drastically reduces MTTR.

Delivering Instant Value for SREs and Platform Teams Through a Layered Architecture

Infrastructure 360 is inherently part of the New Relic platform, built directly on top of our existing capabilities. We engineered it around a two-tiered layered model:

• Core/Base Infrastructure Observability (The Foundation): This layer provides the essential tools teams rely on to view the baseline health of their infrastructure entities and attempt to pinpoint the root causes of standard alerts and issues. It is the necessary bedrock of observability.
• Infrastructure 360 (The Advanced Layer): What Infrastructure 360 provides is a significantly deeper level of information built on top of that base. It answers critical contextual questions: What is actually running? How are these components connected together? Where are the instrumentation gaps that represent dangerous blind spots? How did recent configuration changes affect the reliability and performance of the infrastructure?

These advanced insights are what elevate a reactive monitoring tool into a proactive observability platform.

"Unlike legacy monitoring platforms that force engineers to piece together host data across fragmented product silos, New Relic consolidates infrastructure, applications, and logs into a single, unified database," said New Relic CTO Michael Frendo. "With Infrastructure 360, we leverage this single-source-of-truth architecture to track exact configuration changes and deep cross-stack dependencies in real time. By eliminating the blind spots and data friction common in multi-tool setups, we deliver the rock-solid, high-fidelity telemetry engine required to keep complex production AI applications running with absolute stability and predictability."

Creating Full Architectural Visibility Across Multi-Cloud Estates

In complex multi-cloud environments, engineering teams often spend critical time manually mapping application dependencies during severe outages. When SREs and application developers navigate to a traditional APM summary page, visibility is typically restricted to basic database or host connections, obscuring underlying cloud networks, load balancers, and application gateways.

New Relic Infrastructure 360 provides platform engineers, SREs, and developers with an automated, end-to-end line of sight across hybrid, multi-region, and multi-cloud estates—including Kubernetes environments like Amazon EKS and Azure AKS. Infrastructure 360 gives teams the rich context required to drastically reduce MTTR. It establishes an exhaustive topology, visualizing connections from AWS Amazon Application Load Balancer (ALB) and Azure Application Gateways through Kubernetes ingress controllers and containers directly down to specific APM microservices.

Pervasive Intelligence: Accelerate Incident Triage Without Switching Context

A core tenet of the Infrastructure 360 design is centered around its dedicated, aggregated landing page that serves as a central front-end hub for complete multi-cloud visibility. From this unified landing page, platform engineers and SREs gain a comprehensive view of active alerts, cloud resource inventories, and cross-layer relationships.

Infrastructure 360 introduces a dual workflow model that brings unified visibility for platform engineering, infrastructure, and operations teams across reliability, cost, and security lenses. Platform engineers and developers can utilize familiar workflows for standard troubleshooting, then pivot into the dedicated Infrastructure 360 UI for deep relationship mapping. Also, Infrastructure 360 injects deep dependency mapping and cloud configuration change insights directly into individual entity pages. Whether an SRE or developer is inspecting an APM service, an infrastructure resource, or catalog views, rich architectural context is immediately accessible within their current workspace.

This experience begins at onboarding. Infrastructure 360 establishes a single unified scope across cloud providers, simplifying account connections at the organizational level to streamline management and accelerate onboarding.

Driving Measurable Outcomes: Automated Discovery, Topology, and Change Tracking

Infrastructure 360 equips SREs, platform engineers, and developers to eliminate operational friction through three key capabilities:

1. Resource Discovery & Instrumentation Gaps: Eliminating unmonitored shadow IT by agentlessly discovering AWS and Azure assets and nudging teams to close instrumentation gaps.
2. Relationship Establishment: Unifying cross-layer topology maps to immediately surface incident blast radius across cloud networks and Kubernetes gateways, preventing cross-team finger-pointing and accelerating root cause analysis.
3. Configuration Change Tracking: Tracking how manual or automated configuration edits result directly in reliability issues.

Configuration Changes & The Configuration Explorer

When an issue occurs, the first question is almost always, "What changed?" Infrastructure 360 addresses this directly by automating the tracking of configuration changes across the entire infrastructure footprint. Instead of manually cross-referencing deployment logs and cloud consoles, changes are tracked and surfaced directly within the context of the affected entity.

To accelerate triage, the Configuration Explorer provides side-by-side version differences that drive instant property-level analysis. Rather than just noting that a change happened, engineers can click into a specific event and view exact property-level configuration differences. For example, if an Application Load Balancer's Security Group was modified, the Configuration Explorer reveals the exact change. Furthermore, change tracking events are surfaced directly within active alert views, enabling platform engineers, SREs, and application developers to seamlessly correlate a spike in application errors with a recent infrastructure deployment to resolve root causes in seconds.

Deep Relationships: Visualizing True Structural Blast Radius for Faster Triage

The second pillar is the establishment of deep relationships. As noted, previous monitoring often stopped at the application-to-database level. By mapping how infrastructure resources relate to each other and to the workloads on top of them, Infra 360 surfaces the true blast radius of an anomaly — what's affected, and what's next.

By directly embedding dependency intelligence into individual entity views, platform engineers and developers investigating a slow service can assess incident severity based on the blast radius and impacted resources, confirming if the underlying cause stems from a saturated network component or misconfigured security group.

Empowering the AI Future: The Foundation for Autopilot

The design of Infrastructure 360 is about building the essential foundation necessary for tomorrow's automation. It provides the graph data and change context that feeds AI agents, ensuring Autopilot doesn't hallucinate root causes during automated remediation, enabling it to serve as the ultimate data foundation for AI.

For platform leaders, SREs, and developers, this provides a zero-maintenance telemetry foundation to partner with New Relic Autopilot. When teams integrate Infrastructure 360, Autopilot achieves significantly higher accuracy by ingesting exact topology maps and property differences to pinpoint root causes and recommend targeted remediation actions. With this rich contextual data, Autopilot makes reliable, context-aware decisions. Infrastructure 360 ensures that its visibility directly enhances automated remediation tools, standing as an indispensable layer for scaling observability maturity.

Frequently Asked Questions about New Relic Infrastructure 360

What is New Relic Infrastructure 360?

Infrastructure 360 is an advanced layer built on the New Relic platform that provides automated multi-cloud resource discovery, end-to-end dependency mapping (from cloud gateways and Kubernetes ingress down to APM microservices), and configuration change tracking to drastically reduce MTTR.

When will Infrastructure 360 be available?

Infrastructure 360 is available to customers in Public Preview (PP) starting October 13, 2026.

How does Infrastructure 360 integrate with New Relic Autopilot?

Infrastructure 360 supplies precise graph data, topology maps, and property-level configuration change context that feeds New Relic Autopilot, enabling accurate, automated remediation without hallucinations.

Experience the future of infrastructure observability today with New Relic Infrastructure 360:

Introduction to Infrastructure 360

Get started free

Request a demo