Step 3: Verify Configuration

You can verify that your database has been attached by checking the heroku config of the collector application:

heroku config -a testapp-pganalyze-collector

This will output something like the following:

=== testapp-pganalyze-collector Config Vars
MYDB_PRIMARY_URL: postgres://...:...@...:.../...
PGA_API_KEY: ...

Now, you can verify the configuration by running the test command:

heroku run -a testapp-pganalyze-collector -- collector --test

This should output something similar to the following:

Running collector --test on ⬢ testapp-pganalyze-collector... up, run.7708
2024/09/23 08:58:49 I Running collector test with pganalyze-collector 0.58.0
2024/09/23 08:58:49 I [DATABASE_URL] Testing statistics collection...
2024/09/23 08:58:50 I [DATABASE_URL]   Test collection successful for PostgreSQL 16.2 on aarch64-unknown-linux-gnu, compiled by aarch64-unknown-linux-gnu-gcc (GCC) 9.5.0, 64-bit
2024/09/23 08:58:50 I [DATABASE_URL]   Test snapshot successful
2024/09/23 08:58:50 I [DATABASE_URL] Testing activity snapshots...
2024/09/23 08:58:50 I [DATABASE_URL]   Test snapshot successful
...

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.

Couldn't find what you were looking for or want to talk about something specific?
Start a conversation with us →