Last updated 7 months ago

You can send pgmetrics reports to pgDash regularly, to let pgDash extract and store metrics from those reports.

Typically, you’ll collect the metrics from all important/interesting/related databases from one server in one go, storing it under one name:

pgmetrics {options..} {dbs..} | pgdash prod-23

Avoiding Password Prompt

Running in an automated manner naturally requires avoiding the password prompt that pgmetrics brings up by default. You can use the --no-password option of pgmetrics to suppress this prompt, then setup alternate ways to authenticate. Using .pgpass files to supply the password and/or configuring your pg_hba.conf file to not require password for a particular host/user/database combination are common options.

For more information see pgmetrics invocation options and client autentication chapter in the Postgres docs.

Collecting and Reporting Metrics Periodically

How often you collect and report metrics depends on your database activity. We recommend a frequency like once an hour, especially if you have a lot of databases/tables to collect metrics from.

You can run the command above (“pgmetrics | pgdash”) as a cron job, or use a simple script:

while true
pgmetrics {options..} {dbs..} | pgdash -a APIKEY report NAME
sleep 3600