PostgreSQL with Database Observability

Database Observability gives you deep visibility into PostgreSQL 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 `pg_stat_statements` and `pg_stat_activity`
What you see	Top queries by duration, explain plans with cost highlighting, wait events, query samples
Supported variants	Self-managed PostgreSQL 14+, Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure Database

What you’ll get

Queries Overview dashboard showing RED metrics for every query
Explain plans with visual graphs showing scan types, join strategies, and cost distribution
Wait events categorized by I/O, lock, and network waits from pg_stat_activity
Query samples with individual execution timing and parameters
Table schemas showing structures, indexes, and constraints

Before you start

A few things to keep in mind:

PostgreSQL 14 or later is required.
The pg_stat_statements extension must be installed, which requires a database restart the first time.
You’ll need a monitoring user with the pg_monitor and pg_read_all_stats roles.

The learning path below walks you through each step.

Learning path

PostgreSQL Database Observability

Set up Grafana Cloud Database Observability for PostgreSQL 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 PostgreSQL, this is where you can set it up. Database Observability reads from pg_stat_statements for aggregate query statistics and pg_stat_activity for active session information. It works with self-managed PostgreSQL, Amazon RDS, Aurora, Google Cloud SQL, and Azure Database.

You’ll get the same powerful tools: a Queries Overview dashboard, visual explain plans with cost-coded nodes, wait events categorized by I/O, lock, and network waits, and query samples with individual timing and parameters.

A few things to keep in mind. PostgreSQL 14 or later is required. The pg_stat_statements extension needs to be installed, which requires a database restart the first time. And you’ll need a monitoring user with the pg_monitor and pg_read_all_stats roles.

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

PostgreSQL with Database Observability