Step 5: Configure the Collector

The collector configuration file lives in /etc/pganalyze-collector.conf, and looks like this:

[pganalyze]
api_key = your_pga_organization_api_key

[server1]
db_host = your_database_host
db_port = your_database_port
db_name = your_database_name
db_username = your_monitoring_user
db_password = your_monitoring_user_password

Fill in the values from the info in your Aiven console:

1. The api_key can be found in the pganalyze Settings page for your organization, under the API keys tab
2. The db_host is the hostname of your PostgreSQL instance (example.aivencloud.com above)
3. The db_port is the port your PostgreSQL server is running on (12448 above)
4. The db_name is the database you want to monitor (defaultdb above--make sure this is the same database where you created the pg_stat_statements extension in Step 2)
5. The db_username and db_password should be the credentials of the monitoring user we created in Step 1

Testing the new configuration

Run the following to make sure the configuration works:

sudo pganalyze-collector --test

Once you've confirmed the install is successful and you're receiving query data in pganalyze, we recommend setting up Log Insights as a follow-up step, to automatically track log events in your database.