![]() Multiple storage partitioning layouts available depending on the amount of servers to be monitored. Two most common deployment options are: The Configuration DB centric "pull" modelįor storing metrics collected by the pgwatch2 daemon there are quite some options available: Well reuse your existing PostgreSQL or Grafana installations, adding only pgwatch2 specific components - see here Pgwatch2 can be deployed in various configurations, as all components are "loosely coupled". Log parsing capabilities when deployed locally in "push" modeĬomponent diagram for the default Docker setup. ![]() Very low resource requirements for the collector - 1 CPU core can handle ~3k monitored DBs at 1GB RAM usage.Security options like SSL / HTTPS for all connections and password encryption for connect strings.Internal health-check API to monitor metrics gathering status.PgBouncer, Pgpool-II, AWS RDS and Patroni support.Kubernetes/OpenShift ready with sample templates and a Helm chart.Global or DB level configuration of metrics/intervals.Possible to monitoring all or a subset of DBs of a PostgreSQL cluster.Multiple configuration options (YAML, PostgreSQL, ENV) supporting both "push" and "pull" models.4 supported data stores for metrics storage (PostgreSQL with or without TimescaleDB, InfluxDB, Graphite, Prometheus).Easy extensibility by defining metrics in pure SQL (thus they could also be from business domain).Lots of pre-configured dashboards and metric configurations covering all Statistics Collector data.Intuitive metrics presentation using the Grafana dashboarding engine with optional Alerting.Non-invasive setup, no extensions nor superuser rights required for the base functionality.The behaviour of the Docker images can be customized in many ways - for a complete list of all supported Docker environment NB! If you don't want to add the "test" database (the pgwatch2 configuration db) for monitoring, remove the NOTESTDB=1 env ![]() For defining your own dashboards you need to log in as admin (admin/pgwatch2admin). # and the internal configuration and metrics DB on localhost port 5432ĭocker run -d -restart=unless-stopped -name pw2 \ # fetch and run the latest Docker image, exposing Grafana on port 3000, the administrative web UI on port 8080
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |