Monitor your PostgreSQL databases

Planned: you connect a PostgreSQL database in Pulse and see how it behaves, without changing your application.

What is planned

A Connect wizard in Pulse. You choose where the database runs (your own server or a managed service), install a small agent with one command, get the monitoring role as ready SQL, and check the connection.
An agent in your network that only connects outward. Pulse never reaches into your databases. Passwords stay beside the agent by default.
Read-only access with minimal privileges. A superuser is not needed.
Values stay on your host. Query text is normalised in the agent: literals and bind parameters are replaced before anything is sent.
What you will see. Load as average active sessions by wait type, the sessions of any moment with the blocking tree, queries with calls, time, rows, waits and plans, recommendations (unused indexes, sequential scans, vacuum, long transactions, lock waits), and monitor templates on the postgresql.* metrics.
Links from traces. A database span in a trace opens the query it ran.

Other engines (MySQL and MariaDB, Redis and Valkey, MongoDB, ClickHouse, queues) follow later. See Integrations catalog.