A Zabbix monitoring template for PostgreSQL databases, supporting replication, pgpool-II, and cluster monitoring.
pg_monz is a Zabbix monitoring template specifically designed for PostgreSQL databases. It provides comprehensive monitoring capabilities including health checks, resource usage, performance metrics, and support for advanced configurations like streaming replication and pgpool-II clusters. It solves the problem of setting up detailed, automated database observability within the Zabbix monitoring platform.
Database administrators and DevOps engineers who manage PostgreSQL databases and use Zabbix for infrastructure monitoring.
Developers choose pg_monz because it offers a specialized, feature-rich template that simplifies monitoring complex PostgreSQL setups, including replication and pgpool-II, with automatic discovery and performance-optimized data collection directly within Zabbix.
This is the Zabbix monitoring template for PostgreSQL Database.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Monitors PostgreSQL connections, transactions, logs, sizes, slow queries, and supports streaming replication and pgpool-II integration, as detailed in the application groupings like pg.transactions and pg.sr.status.
Uses Zabbix discovery to automatically detect and start monitoring databases and tables, reducing manual configuration efforts, as highlighted in the README's key features.
Reduces database connection frequency by batching item collection, minimizing performance impact on PostgreSQL instances, as noted in the performance improvements section for version 2.0.
Supports monitoring of PostgreSQL + pgpool-II clusters, including split-brain detection and failover triggers, ideal for complex high-availability setups described in the cluster monitoring section.
Maintenance ended in October 2021, meaning no updates, bug fixes, or official support, which risks compatibility with newer software versions and security issues.
Requires specific versions of Zabbix, PostgreSQL, and pgpool-II, and lacks backward compatibility with version 1.0, necessitating a full reinstall for upgrades as stated in the installation notes.
Exclusively designed for Zabbix, making it unsuitable for teams using other monitoring tools like Prometheus or Datadog, limiting flexibility in mixed-infrastructure environments.