-
Notifications
You must be signed in to change notification settings - Fork 29
Setup for regular users
IMPORTANT: This tutorial is intended for using by non-Weaponry users.
In this tutorial we are going to configure system and install pgSCV from .tar.gz
archive on Ubuntu 20.04.
- create dedicated monitoring roles in Postgres and Pgbouncer (optional)
- install pgSCV from
tar.gz
on Ubuntu 20.04 Finally, pgSCV will be run underpostgres
user with disabled auto-update feature.
Make sure PostgreSQL service should be installed and running. The ps
command should show running Postgres processes:
ps f -u postgres
PID TTY STAT TIME COMMAND
3283 ? Sl 0:00 /usr/sbin/pgbouncer -d /etc/pgbouncer/pgbouncer.ini
3184 ? Ss 0:00 /usr/lib/postgresql/13/bin/postgres -D /var/lib/postgresql/13/main -c config_file=/etc/postgresql/13/main/postgresql.conf
3186 ? Ss 0:00 \_ postgres: 13/main: checkpointer
3187 ? Ss 0:00 \_ postgres: 13/main: background writer
3188 ? Ss 0:00 \_ postgres: 13/main: walwriter
3189 ? Ss 0:00 \_ postgres: 13/main: autovacuum launcher
3190 ? Ss 0:00 \_ postgres: 13/main: stats collector
3191 ? Ss 0:00 \_ postgres: 13/main: logical replication launcher
Connect to Postgres and create database user for pgSCV. This could be unprivileged user with special server roles which allow pgSCV read statistics and traverse directories and files.
sudo -u postgres psql
postgres=# CREATE ROLE pgscv WITH LOGIN PASSWORD 'SUPERSECRETPASSWORD';
postgres=# GRANT pg_read_server_files, pg_monitor TO pgscv;
postgres=# GRANT EXECUTE on FUNCTION pg_current_logfile() TO pgscv;
Created user should be allowed to connect to Postgres through UNIX sockets and localhost. Add the following lines to pg_hba.conf
:
local all pgscv md5
host all pgscv 127.0.0.1/32 md5
Exact path to pg_hba.conf
depends on Postgres version. Default path on Ubuntu is version-specific directory inside /etc/postgresql/
.
After adding lines to pg_hba.conf
, Postgres service should be reloaded. Connect to Postgres and execute pg_reload_conf()
function.
sudo -u postgres psql -c 'select pg_reload_conf()'
Now, test the connection using created database role using psql
utility. Specify the password in environment variable.
PGPASSWORD=SUPERSECRETPASSWORD psql -h 127.0.0.1 -U pgscv -d postgres -c "SELECT version()"
version
----------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 13.2 (Ubuntu 13.2-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, 64-bit
In this example we connect to Postgres and ask its version.
In case of using Pgbouncer, additional configuration have to be made. Add pgscv
user to stats_users
list in pgbouncer.ini
stats_users = pgscv
After changing pgbouncer.ini
, Pgbouncer service should be reloaded.
systemctl reload pgbouncer
Depending on used auth_type
user and password should be specified in auth_file
. By default, it is userlist.txt
. For example for auth_type = md5
, user and password could be added in the following way:
echo -n "SUPERSECRETPASSWORD" |md5sum |awk -v user=pgscv '{printf "\"%s\" \"md5%s\"\n", user, $1}' >> /etc/pgbouncer/userlist.txt
Now, make test connection to Pgbouncer. Specify the password in environment variable.
PGPASSWORD=SUPERSECRETPASSWORD psql -h 127.0.0.1 -p 6432 -U pgscv -d pgbouncer -c "SHOW version"
version
------------------
PgBouncer 1.15.0
In this example we connect to Pgbouncer built-in database and ask its version.
Download the deb
package and install it using dpkg
utility. In this tutorial, v0.6.0 is used, check out the latest version in releases page.
wget https://github.com/weaponry/pgscv/releases/download/v0.6.0/pgscv_0.6.0_linux_amd64.tar.gz
tar xvzf pgscv_0.6.0_linux_amd64.tar.gz
sudo cp pgscv /usr/bin/pgscv
Create pgSCV default configuration in /etc/pgscv.yaml
with the credentials created in previous steps.
defaults:
postgres_username: "pgscv"
postgres_password: "SUPERSECRETPASSWORD"
pgbouncer_username: "pgscv"
pgbouncer_password: "SUPERSECRETPASSWORD"
Create a unit file for systemd service /etc/systemd/system/pgscv.service
with the following content:
[Unit]
Description=pgSCV is the Weaponry platform agent for PostgreSQL ecosystem
Requires=network-online.target
After=network-online.target
[Service]
Type=simple
User=postgres
Group=postgres
# Start the agent process
ExecStart=/usr/bin/pgscv --config-file=/etc/pgscv.yaml
# Kill all processes in the cgroup
KillMode=control-group
# Wait reasonable amount of time for agent up/down
TimeoutSec=5
# Restart agent if it crashes
Restart=on-failure
RestartSec=10
# if agent leaks during long period of time, let him to be the first person for eviction
OOMScoreAdjust=1000
[Install]
WantedBy=multi-user.target
Reload systemd and start pgSCV service.
systemctl daemon-reload
systemctl enable pgscv
systemctl start pgscv
Check pgSCV status using journalctl
. There should be no errors.
journalctl -fu pgscv
Mar 31 08:20:09 ubuntu-pgscv-test systemd[1]: Started pgSCV is the Weaponry platform agent for PostgreSQL ecosystem.
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"read configuration from /etc/pgscv.yaml"}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"*** IMPORTANT ***: pgSCV by default collects information about user queries. Tracking queries can be disabled with 'no_track_mode: true' in config file."}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"no-track mode disabled"}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"accepting requests on http://127.0.0.1:9890/metrics"}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"auto-discovery: service added [system:0]"}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"auto-discovery [postgres]: service added [postgres:5432]"}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"auto-discovery [pgbouncer]: service added [pgbouncer:6432]"}
Mar 31 08:20:09 ubuntu-pgscv-test pgscv[5673]: {"level":"info","service":"pgscv","time":"2021-03-31T08:20:09+02:00","message":"pg_stat_statements is not found in shared_preload_libraries, disable pg_stat_statements metrics collection"}
Connect to pgSCV using curl
and ask metrics, there should be non-zero counts.
curl -s http://127.0.0.1:9890/metrics | grep -c ^postgres
411
curl -s http://127.0.0.1:9890/metrics | grep -c ^pgbouncer
100
curl -s http://127.0.0.1:9890/metrics | grep -c ^node
288
curl -s http://127.0.0.1:9890/metrics | grep -c ^go
34
In case of errors, see troubleshooting notes