---
title: "Database Observability: Is it right for you | Grafana Labs"
description: "Decide whether Database Observability fits your databases, incident workflows, and cost goals."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Is it right for you?

Database Observability meets your needs when you:

- Have application traces that stop at the database boundary. You can see a query is slow, but not what inside the database is causing it.
- Run MySQL or PostgreSQL on RDS or Aurora
- Have developers and SREs spending incident time waiting for a DBA to investigate database problems, and that bottleneck is slowing resolution
- Are already using Grafana Cloud for application or infrastructure observability, and the database layer is a blind spot
- Are paying a per-host premium for database monitoring, and the bill grows every time you add an instance