Introducing Database 360: Full-Stack Database RCA in One Place

When production latency spikes, the first question is almost always the same: is it the app, the database, or the infrastructure? Too often, answering it means jumping between dashboards, database consoles, and infrastructure views—while teams debate where to look next.

Today at New Relic Advance, we’re announcing the preview of Database 360 (DB360)—a unified database experience that brings database query telemetry and full-stack context together, so you can pinpoint performance issues faster and resolve them with less back-and-forth.

DB360 is differentiated because it connects the dots across your stack. It models databases as first-class entities linked to the services and infrastructure that depend on them, then brings the most important diagnostic signals—like query details, explain plans, waits, and locks—into one workflow. In practice, that means you can quickly answer: what changed, what’s impacted, and what to fix next—without switching tools.

Full-stack database root cause analysis in one place

Database performance issues rarely live in one domain. A slow transaction can be caused by a query regression, blocking locks, resource saturation, or a change upstream in the application. DB360 brings the core signals together so teams can move faster from detection to root cause.

With DB360, you can:

You now have an intuitive UI to view all your slow queries, the ability to drill down into the details, see historical stats , see which applications fired the query, see if the query was waiting for resources/locks to be released, visualize execution plans and plan drifts and see infra metrics all in one place - helping you quickly isolate the cause of the problem without switching tools and views.

Additionally you know have the ability to see slow transactions happening on the APM page and directly jump into the how the query behaved within the database - instantly exposing database internal data to APM users. 

• Start from a database entity view and immediately see the services, hosts, and clusters connected to it
• Drill into slow queries with explain plans and supporting context like waits and locks
• Validate whether the bottleneck is inside the database or tied to underlying infrastructure constraints

Faster triage when multiple teams are involved

Database incidents often become “handoff incidents”—Dev, SRE, and DB teams each have partial views and spend time reconciling facts. DB360 reduces that friction by presenting database behavior in the same context teams already use to troubleshoot application and infrastructure performance.

That shared context helps teams quickly align on:

• Which services are impacted
• Which queries are contributing most to load or latency
• Whether waits/locks or infrastructure saturation is driving the slowdown

Proactive protection against “noisy neighbor” and shared-instance risk

Shared database environments introduce a common reliability risk: one workload consumes disproportionate resources, degrading performance for others. DB360 helps surface early warning signals by highlighting long-running sessions, blocking queries, and resource-heavy behavior so teams can address issues before they become major incidents.

Image: (Insert screenshot of sessions/locks view highlighting blockers and affected consumers.)

Performance, reliability, and cost recommendations—so you know what to fix next

Teams don’t just want visibility—they want direction. DB360 includes recommendations across performance, reliability, and cost so you can prioritize the changes that will have the biggest impact.

Examples include:

• Performance guidance like missing indexes
• Reliability flags like low disk space or elevated risk indicators
• Cost signals such as idle or underutilized managed instances

Getting started with Database 360 (two-step workflow)

Open DB360 from your database monitoring view

If you’re already using Database Performance Monitoring, you can jump straight into DB360 from your database experience. Start with the database entity view to quickly see what’s connected—the services that depend on the database and the infrastructure supporting it.

Pinpoint root cause with query + context in one workflow

When latency spikes, use DB360 to move from symptom to cause without switching tools:

• Identify the highest-impact slow query
• Review the explain plan
• Check waits/locks for contention
• Confirm whether infrastructure constraints are contributing