A flexible, self-contained PostgreSQL metrics monitoring and dashboarding solution supporting versions 9.0 to 16.
pgwatch2 is a flexible, self-contained monitoring and dashboarding solution specifically designed for PostgreSQL databases. It provides deep insights into database performance and health by collecting metrics without requiring invasive setup or superuser privileges, and integrates with Grafana for visualization.
Database administrators and developers managing PostgreSQL databases from versions 9.0 to 16, including those using AWS RDS, PgBouncer, Pgpool-II, or Patroni, who need comprehensive monitoring with minimal overhead.
Developers choose pgwatch2 for its non-invasive setup that doesn't require extensions or superuser rights, its extensibility through pure SQL metric definitions, and its support for multiple deployment models and data stores like PostgreSQL, InfluxDB, and Prometheus.
PostgreSQL metrics monitor/dashboard
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Requires no extensions or superuser privileges for base functionality, making it safe for production databases without invasive changes, as highlighted in the README.
Allows defining custom metrics using pure SQL queries, enabling collection of business-specific data alongside system metrics, with support for version-specific queries.
Supports both centralized pull and decentralized push configurations, with options for YAML, PostgreSQL, or environment-based setup, catering to diverse infrastructure needs.
Monitors PostgreSQL versions from 9.0 to 16 out of the box, and includes support for PgBouncer, Pgpool-II, AWS RDS, and Patroni, as stated in the features.
The collector is efficient, handling approximately 3,000 databases per CPU core with only 1GB of RAM, making it suitable for large-scale deployments.
The project is now archived with no further development, which could lead to compatibility issues with future PostgreSQL versions or dependencies, as noted in the README warning.
Does not support InfluxDB 2.0, restricting options for teams using the latest time-series database versions, as admitted in the metrics storage section.
Accessing protected statistics requires installing helper functions or granting specific roles like pg_monitor, adding complexity compared to more integrated monitoring solutions.
Relies on Grafana for visualization and alerting, which might require additional setup and maintenance, especially if not already part of the existing stack.