All activity
Muhammad samileft a comment
I’m building pgSentry, a PostgreSQL micro-DBA designed for teams that don’t have a dedicated DBA (or engineers who want quicker, clearer DB visibility). You connect your Postgres cluster using a read-only user, and pgSentry will automatically analyze key health areas like tables, indexes, bloat/vacuum signals, replication lag/WAL/slots, locks, and slow query patterns, then suggest improvements...
pgSentryPostgreSQL-only. The micro-DBA for modern engineering teams
Postgres often fails silently (bloat, replication lag/WAL growth, inactive replication slots, slow query regressions, blocking locks). pgSentry watches your DB and turns those signals into a clear dashboard + severity-ranked, actionable recommendations (with copy-paste SQL fixes) — before they become incidents.
Works with AWS RDS, Supabase, Neon, Google Cloud SQL, and self-hosted.
pgSentryPostgreSQL-only. The micro-DBA for modern engineering teams
Muhammad samistarted a discussion
PostgreSQL micro-DBA: catch lag, bloat & slow queries before incidents
pgSentry is PostgreSQL-only monitoring that detects replication lag/WAL slot risk, bloat, blocking locks, and slow query regressions — then provides severity-ranked alerts and actionable fixes (copy-paste SQL). Works with RDS, Supabase, Neon, Cloud SQL, and self-hosted.