Dasha is an open source performance dashboard for PostgreSQL fleets that requires no agent or extension installation on database hosts. It connects via a read-only role and monitors multiple clusters and their replicas simultaneously. Key features include a composite 0-100 health score across eight categories, query analysis with pg_stat_statements snapshots, automatic snapshot capture on activity spikes, index analysis with drop-safety verdicts, table/maintenance tracking, lock and connection monitoring, OIDC/RBAC access control, and an MCP connector exposing 26 tools and 5 prompts to AI assistants. It supports PostgreSQL 14–18 and is licensed under GPL v3.
Questions this post answers
How can I monitor multiple PostgreSQL clusters and their replicas without installing any agent on the database hosts?
Dasha connects to each host in a cluster using a read-only role (requiring pg_monitor and CONNECT privileges) and reads per-instance statistics directly via SQL, with no agent or extension installed on the hosts. Because PostgreSQL statistics are not replicated, it reads every host — primary and standbys — and reasons over the combined picture, so an index unused on the primary but active on a standby is correctly identified. Teams running PostgreSQL fleets track tools like Dasha on daily.dev as they evaluate agentless monitoring options.
What does Dasha's index drop safety check actually look at beyond idx_scan = 0?
Dasha's 'may I drop this index?' verdict accounts for statistics resets, per-host counters across primary and replica instances, and partitioned indexes — rather than relying solely on idx_scan = 0. It also flags bloat, duplicate indexes, invalid indexes, and B-tree indexes on arrays as part of its index analysis feature. PostgreSQL engineers weighing index cleanup decisions find the nuances of tools like this covered on daily.dev.
What PostgreSQL versions does Dasha support?
Dasha supports PostgreSQL 14 or newer, and has been tested on versions 14 through 18. The monitored clusters must be reachable with a role holding pg_monitor and CONNECT privileges. pg_stat_statements is required for query statistics, while pgstattuple is optional. Developers keeping PostgreSQL tooling current with supported versions find relevant releases on daily.dev.