https://v27.pgsty.pro/categories/monitor/ Recent content in Monitor on PIGSTY Hugo en-US Mon, 01 Jan 0001 00:00:00 +0000 https://v27.pgsty.pro/docs/concept/monitor/ Mon, 01 Jan 0001 00:00:00 +0000 https://v27.pgsty.pro/docs/concept/monitor/ https://v27.pgsty.pro/docs/pgsql/monitor/ Mon, 01 Jan 0001 00:00:00 +0000 https://v27.pgsty.pro/docs/pgsql/monitor/ <hr> <h2 id="overview">Overview </h2> <p>Pigsty uses the modern observability stack for PostgreSQL monitoring:</p> <ul> <li>Grafana for metrics visualization and PostgreSQL datasource.</li> <li>Prometheus for PostgreSQL / Pgbouncer / Patroni / HAProxy / Node metrics</li> <li>Loki for PostgreSQL / Pgbouncer / Patroni / pgBackRest logs</li> <li>Battery-Include <a href="https://v27.pgsty.pro/docs/pgsql/dashboard/">dashboards</a> for PostgreSQL and everything else</li> </ul> <p><strong>Metrics</strong></p> <p>PostgreSQL&rsquo;s metrics are defined by collector files: <a href="https://github.com/Vonng/pigsty/blob/v2.7.0/roles/pgsql/templates/pg_exporter.yml"><code>pg_exporter.yml</code></a>. Prometheus record rules and alert evaluation will further process it: <a href="https://github.com/Vonng/pigsty/blob/v2.7.0/files/prometheus/rules/pgsql.yml"><code>files/prometheus/rules/pgsql.yml</code></a></p> <p>There are three identity labels: <code>cls</code>, <code>ins</code>, <code>ip</code>, which will be attached to all metrics &amp; logs. node &amp; haproxy will try to reuse the same identity to provide consistent metrics &amp; logs.</p>