New Relic Database 360 reaches general availability for database root cause analysis

One view for applications, databases and infrastructure

New Relic says Database 360 models databases as first-class entities that are connected directly to APM services and infrastructure. The product is built on an OpenTelemetry-first foundation and offers curated workflows for diagnosing performance problems.

The company argues that database monitoring has historically been disjointed. Organizations often pay a premium for legacy point solutions to watch database health while using separate tools for APM. When something goes wrong, according to New Relic, there is no native correlation between a slow application trace and the database wait event or lock behind it. The company also says proprietary monitoring agents often tie customers to billing models that penalize the collection of high-cardinality metrics such as detailed execution plans.

Database 360 natively links database entities to APM services, with Java and .NET currently supported. Teams can view query details, visual execution plans, wait states, locks and infrastructure metrics in one context, and see whether a problem originates in the application code, the query structure or the underlying host.

OpenTelemetry collection, tool consolidation and workload control

Data collection relies on standard OpenTelemetry for major relational database engines, through either the New Relic OTel collector (NRDOT) or the CNCF OTel public contrib repositories. New Relic says this gives customers full control over their telemetry and avoids lock-in to proprietary agents.

The company also positions the product as a way to replace specialized point tools and overlapping licenses with one platform shared by DBAs and developers. Pricing is based on data ingest, which New Relic describes as predictable, without compute licenses or custom metric penalties.

Further capabilities named in the announcement:

• Noisy-neighbor prevention: detection of long-running sessions, blocking queries and resource-heavy workloads, so a single runaway query does not monopolize a database node.
• Capacity optimization: metrics to help identify oversized or underused managed database instances, such as large, under-utilized AWS RDS deployments.
• Client visibility: the product ties into applications that send queries and classifies incoming queries, showing the behavior of each connected client or application on the database.

Supported database engines

New Relic describes the release as a significant step up from its earlier database plugins. For MySQL (8.0.3+) and PostgreSQL (14+), it is introducing completely new OpenTelemetry (NRDOT) integrations. These bring first-class database entities, query plans, and wait and lock states linked directly to APM.

For Oracle (19c+) and MS SQL (2017+), the company is delivering major upgrades over its previous plugins. According to New Relic, these include deep OTel metric collection, explain plan correlations, granular session tracking and curated root cause analysis workflows.

What it means for engineering teams

For teams that run separate database and application monitoring tools, Database 360 is New Relic's answer to a familiar problem: slow queries that several groups must investigate from different data. By placing execution plans, performance metrics and wait states in one place, the company says Dev, SRE and DB teams can resolve issues faster and with less friction between them.

The OpenTelemetry-first approach and ingest-based pricing target organizations wary of proprietary agents and unpredictable costs. The current APM linkage covers Java and .NET only, which defines the scope of the full application-to-database correlation at launch. New Relic offers a free starting option and a demo request on its site.