Skip to content

vadv/pg_gatherer

Repository files navigation

pg_gatherer

The project is designed to collect and store statistical data of PostgreSQL into other PostgreSQL.

Architecture

           +------------+               +---------------+
       +---+   Grafana  |          +--->+  Target # 1   |
       |   +------------+          |    +---------------+
       v                           |
+------+-------+                   |    +---------------+
|   Storage    |     +-------------+--->+  Target # N   |
+------+-------+     |                  +---------------+
       ^             |
       |     +-------+--------+         +---------------+
       +-----+   pg_gatherer  +<--------+  Prometheus   |
             +---------+------+         +---------------+
                       |
+----------------+     |         +-----------------------+
|Pager Dutty Api +<----+-------> | Other api (zabbix, ..)|
+----------------+               +-----------------------+

Targets

Target databases, which agent is monitored.

Storage

PostgreSQL database (recommended use TimescaleDB extension) in which information is stored.

Agent pg_gatherer

The agent is golang-binary, with plugins written in Gopher-lua (without any system dependencies).

You can run agent locally on machine Target, then you get additional statistics, for example link /proc/{pid}/io stats with query.

Why?

There are a lot of monitoring systems in the world that are known and proven. Why make another system?

The answers:

  • firstly pg_gatherer does not claim to be a full-fledged monitoring system, it developed as a tool for in-depth analysis.
  • it seems natural to me to store different information (not only float/int metrics with tags) but also queries texts in the database.
  • system should be easily extensible with plugins.
  • keep integration with Grafana.

Installation

  • Install storage database.
  • Apply migration on storage database.
  • Create user on targets with pg_monitor rights.
  • Get && run agent.
  • Populate table host on storage database.
  • Also, if you use TimescaleDB, when you can use Grafana dashboard.
go get github.com/vadv/pg_gatherer/gatherer/cmd/pg_gatherer
pg_gatherer \
    --host-config-file host-config.yaml \
    --plugins-dir /etc/pg_gatherer/plugins \
    --cache-dir /var/cache \
    --http-listen 8080 \
    --secret-file /path/to/secrets.yaml \
    --max-open-conns 1

Host config example:

peripheral-db-1: # name of target in storage-db

  plugins: # list of plugins which can be activated on this target
    - activity
    - databases
    ...

  connections:
    target: # target agent connection
      host: 192.168.1.1
      dbname: your_database
      username: monitor
      port: 5432
    storage: # storage connection
      host: /tmp
      dbname: gatherer
      username: storage
      port: 5432
    replica: # another target agent connection
      host: 192.168.1.2
      dbname: your_database
      username: monitor
      port: 5432

Plugins

More information here: plugins

Build status

Status