MySQL with Database Observability

Database Observability gives you deep visibility into MySQL query performance, whether your database is self-managed or running on a managed cloud service.


What it monitors	Query performance, explain plans, wait events, query samples, table schemas
How it works	Grafana Alloy reads from MySQL Performance Schema (enabled by default in 8.0+)
What you see	Top queries by duration, explain plans with cost highlighting, wait events, query samples
Supported variants	Self-managed MySQL 8.0+, Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure Database

What you’ll get

Queries Overview dashboard showing RED metrics for every query
Explain plans revealing full table scans, missing indexes, and expensive joins
Wait events showing lock contention, I/O bottlenecks, and resource waits
Query samples with individual execution timing
Table schemas highlighting index coverage and constraints

Before you start

A few things to keep in mind:

MySQL 8.0 or later is required. MariaDB isn’t supported.
You’ll need a monitoring user with specific privileges.
There’s some initial setup before data starts flowing.

The learning path below walks you through each step.

Learning path

MySQL Database Observability

Set up Grafana Cloud Database Observability for MySQL to monitor query performance, explain plans, wait events, and query samples.

13 min

Intermediate

Docs & blog posts

Open in Grafana Cloud

Complete this learning path directly in your Grafana Cloud stack, or in the Grafana Play stack, with an interactive learning experience.

Open in Grafana Cloud Try in Grafana Play

View on website

Path completed

If you’re running MySQL, this is where you can set it up. Database Observability reads from MySQL Performance Schema, which is enabled by default in MySQL 8.0 and later. It works with self-managed MySQL, Amazon RDS, Aurora, Google Cloud SQL, and Azure Database.

You’ll get the full suite: a Queries Overview dashboard with RED metrics, explain plans that highlight full table scans and expensive joins, wait events showing lock contention and I/O bottlenecks, and query samples with individual execution timing.

There are a few trade-offs to consider. MySQL 8.0 or later is required, and MariaDB is not supported. You’ll need a monitoring user with specific privileges, and there’s some initial setup. Once it’s running, you have query-level MySQL visibility, down to individual queries, explain plans, and wait events.

When you’re ready, the learning path below walks you through the setup step by step.

MySQL with Database Observability