New Relic Infrastructure 360 maps cloud dependencies and config changes to cut MTTR

From a CPU alert to the change that caused it

New Relic argues that traditional infrastructure monitoring, which mostly reports that a host is degrading or a CPU threshold has been breached, leaves responders without the broader picture. The company says half of major production outages stem directly from untracked infrastructure changes, and that engineers need a view of downstream dependencies to judge customer business impact.

Its example: an automated deployment alters an Azure Application Gateway rule at 2:00 AM and latency spikes appear across downstream Kubernetes microservices. According to New Relic, Infrastructure 360 correlates the latency alert on the APM entity page to the exact line-item configuration difference on the gateway, so SREs do not have to guess which team's deploy broke the application.

Three stages of diagnostic depth

New Relic describes a progressive triage journey in three stages:

• Surface Health and Alert Context: validate baseline entity health, resource consumption and active alert conditions across a multi-cloud footprint.
• Automated Dependency and Blast Radius Mapping: see how a failing component connects to upstream application gateways, load balancers and downstream microservices.
• Configuration Change Impact Analysis: surface property-level configuration edits made before the anomaly and link them to application performance drops.

The product sits on top of the existing platform in a two-tier model. The base layer, Core Infrastructure Observability, covers baseline health and root-cause work on standard alerts. Infrastructure 360 adds answers to what is actually running, how components are connected, where instrumentation gaps create blind spots, and how recent configuration changes affected reliability and performance.

Topology across AWS, Azure and Kubernetes

New Relic says Infrastructure 360 gives platform engineers, SREs and developers an automated line of sight across hybrid, multi-region and multi-cloud estates, including Kubernetes environments such as Amazon EKS and Azure AKS. The topology runs from AWS Application Load Balancer (ALB) and Azure Application Gateways through Kubernetes ingress controllers and containers down to specific APM microservices. The company contrasts this with a typical APM summary page, where visibility is usually limited to basic database or host connections.

The product has a dedicated aggregated landing page showing active alerts, cloud resource inventories and cross-layer relationships, viewed through reliability, cost and security lenses. Engineers can use familiar workflows for standard troubleshooting and then move into the Infrastructure 360 interface for deeper relationship mapping. Dependency mapping and cloud configuration change insights are also placed directly in individual entity pages, such as APM services, infrastructure resources and catalog views.

For onboarding, New Relic says Infrastructure 360 sets a single unified scope across cloud providers and simplifies account connections at the organizational level. The company also lists agentless discovery of AWS and Azure assets, which it says helps eliminate unmonitored shadow IT and prompts teams to close instrumentation gaps.

Configuration context and AI readiness

The Configuration Explorer provides property-level analysis of configuration edits and correlates them with performance drops. New Relic also says the topology maps and change context that Infrastructure 360 supplies are meant to power New Relic Autopilot for automated remediation.

New Relic CTO Michael Frendo framed the product around the company's single database. "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," he said, according to the company's blog post.

What it means for operations teams

For SREs and platform teams working across several clouds, the pitch is less switching between tools during an outage and quicker answers about what changed and what else is affected. These benefits are New Relic's own claims, and the source does not provide pricing, availability details or measured MTTR results.