Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Splunk Database Monitoring review

#8 of 38 in Database MonitoringDatabase Performance Monitoring Software

A focused cloud service for correlating database, application, and infrastructure performance.

8.4/10Editor score
Splunk Database Monitoring8.4 Visit Splunk

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Splunk Database Monitoring is a cloud service within Splunk Observability Cloud for DevOps, ITOps, and SRE teams that need database performance visibility alongside application and infrastructure data. It focuses on Microsoft SQL Server, MySQL, Oracle Database, and PostgreSQL, with collectors operating in on-host or remote gateway modes for different database environments.

Its strongest capability is the depth of query investigation. Teams can find slow and resource-intensive queries, inspect execution plans, review wait states, analyze blocking sessions and lock contention, and compare query samples with normalized query views. Application trace correlation connects database behavior with Splunk APM, while infrastructure correlation covers host CPU, memory, and I/O through Splunk Infrastructure Monitoring. Generative AI recommendations add guidance for complex SQL queries. This makes the product a strong fit for organizations already working across Splunk's observability products and needing a connected view of database and application performance.

The Database Monitoring plan costs $75 per database instance per month with annual billing. It includes the listed query analytics, correlation features, and generative AI SQL recommendations, but there is no free plan. The service is more narrowly suited to teams using one of the four supported database engines and the Splunk ecosystem than to organizations seeking broad database coverage or an independent monitoring stack. Retention for normalized queries and query samples is 15 days, which may matter to teams requiring longer historical query analysis. Choose it when Splunk correlation and SQL performance investigation are priorities; look elsewhere if those ecosystem requirements or retention boundaries do not fit.

Splunk Database Monitoring pros and cons

  • Where it wins
    • Detailed query, execution-plan, wait-state, and blocking analysis
    • Correlates database behavior with traces and host resource metrics
    • Generative AI recommendations for complex SQL queries
  • Where it doesn't
    • No free plan is available
    • Supports four database engines
    • Normalized queries and samples have 15-day retention

Splunk Database Monitoring fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update