Heroku Postgres is a managed SQL database service provided directly by Heroku. You can access a Heroku Postgres database from any language with a PostgreSQL driver, including all languages officially supported by Heroku.

Heroku Postgres provides database and server metrics that give information on the status of your instance. Understanding and monitoring these metrics ensures the health of your database as your applications run and scale. Monitoring can also help you tune, debug, and troubleshoot your application. If you have a production database, make sure you’re monitoring it.

In this getting started, you learn how to:

• View PostgreSQL logs
• Review monitoring add-on options
• Identify which database metrics to track

Before You Begin

You must have a Heroku Postgres database provisioned before you can proceed. Use the heroku addons command to determine whether your app already has Heroku Postgres provisioned:

$ heroku addons
Add-on                                               Plan        Price                           Max Price                       State
───────────────────────────────────────────────────  ──────────  ──────────────────────────────  ──────────────────────────────  ───────
heroku-postgresql (postgresql-elliptical-12345)      standard-0  ~$0.069/hour                    $50/month                       created

To learn how to create a Heroku Postgres database, see Provisioning Heroku Postgres.

Explore Heroku Postgres Logs

You can view logs with the Heroku CLI, the dashboard, or your logging add-on in your log drain in Cedar-generation apps or telemetry drain in Fir-generation apps.

Cedar-Generation Apps

Heroku Postgres logs to the logplex, which collates and publishes your application’s log stream. You can isolate Heroku Postgres events with the heroku logs command by filtering for the postgres process type with the -p flag.

Heroku Postgres metrics logs are emitted with heroku-postgres as the process type:

$ heroku logs -p heroku-postgres -a example-app
2022-04-21T07:46:55.000000+00:00 app[heroku-postgres]: source=HEROKU_POSTGRESQL_COBALT addon=postgresql-demo sample#current_transaction=509 sample#db_size=8426031bytes sample#tables=0 sample#active-connections=11 sample#waiting-connections=0 sample#index-cache-hit-rate=0 sample#table-cache-hit-rate=0 sample#load-avg-1m=0.02 sample#load-avg-5m=0.005 sample#load-avg-15m=0 sample#read-iops=0 sample#write-iops=0.10204 sample#tmp-disk-used=543600640 sample#tmp-disk-available=72435191808 sample#memory-total=3958708kB sample#memory-free=69612kB sample#memory-cached=3405616kB sample#memory-postgres=22080kB sample#wal-percentage-used=0.06428126026622091
...

PostgreSQL logs are emitted with the postgres process type:

$ heroku logs -p postgres -a example-app
2024-03-15T12:37:36.000000+00:00 app[postgres.2966211]: [DATABASE] [12-1]  sql_error_code = 42703 (...)" application_name="psql interactive" ERROR:  column "haiku" does not exist at character 8
...

Use the --tail option to access real-time log entries:

$ heroku logs -p heroku-postgres -a example-app  --tail

When you’re done, press Ctrl+C to return to the prompt. A real-time tail session automatically terminates after one hour of inactivity.

If you don’t want to manually sift through logs, you can install a monitoring add-on.

Fir-Generation Apps

Heroku Postgres signals are available through OpenTelemetry for log collection. Both logs and metrics are emitted in real time with the heroku-postgresql source type:

$ heroku logs -s heroku-postgresql -a example-app
2025-08-20T19:16:10.000000+00:00 heroku-postgresql[logs]: [ORANGE] [13-1]  sql_error_code = 42P01 time_ms = "2025-08-20 19:16:10.974 UTC" pid="28248" proc_start_time="2025-08-20 17:02:06 UTC" session_id="68a5ff8e.6e58" vtid="242/403" tid="0" log_line="8" database="dbjjab162vq6qo" connection_source="204.14.236.211(53777)" user="uf99bg1ci79f3c" application_name="psql" ERROR:  relation "salesforce" does not exist at character 15
2025-08-20T19:16:09.000000+00:00 heroku-postgresql[logs]: source=HEROKU_POSTGRESQL_ORANGE addon=postgresql-curved-71720 sample#service-available=1 sample#current_transaction=1496 sample#db_size=8883347bytes sample#db-max-size=68719476736bytes sample#db-size-percentage-used=0.00013 sample#tables=7 sample#active-connections=15 sample#waiting-connections=0 sample#max-connections=200 sample#connections-percentage-used=0.07500 sample#index-cache-hit-rate=0.99889 sample#table-cache-hit-rate=1 sample#load-avg-1m=0.065 sample#load-avg-5m=0.075 sample#load-avg-15m=0.05 sample#read-iops=0 sample#write-iops=0.023529 sample#max-iops=3000 sample#iops-percentage-used=0.00001 sample#tmp-disk-used=543633408 sample#tmp-disk-available=72435159040 sample#memory-total=3944372kB sample#memory-free=809860kB sample#memory-percentage-used=0.79468 sample#memory-cached=2485000kB sample#memory-postgres=30936kB sample#wal-percentage-used=0.06402297744064274 sample#rollback-from=2025-08-19T17:21
...

Install a Monitoring Add-on

The most effective way to track database metrics is to install a platform monitoring add-on.

A full list of monitoring add-ons can be found on the Heroku Elements Marketplace. Many of these add-ons offer a free plan to get started. See your add-on’s documentation for instructions on retrieving logs.

Review Database Metrics

Heroku Postgres provides database and server metrics that give information on the status of your instance. Understanding and monitoring these metrics ensures the health of your database as your applications run and scale. Monitoring can also help you identify bottlenecks, bugs, and performance issues. You can look for these metrics in the log or in the dashboard for your monitoring add-on.

You can track metrics for the following:

• Database attributes apply to a particular database.
• Server come directly from the server operating system.
• pg_bouncer metrics are included for any Heroku Postgres server that has a PgBouncer pooler attachment. These metrics are a subset of those viewable by running the SHOW POOLS; command when connected to PgBouncer’s special internal database.

For more information about the different available metrics, see Heroku Postgres Metrics Logs. For a list of suggested metrics, see Monitoring Heroku Postgres.

Next Steps

Learn more about monitoring Heroku Postgres databases with the following content:

• Monitoring Heroku Postgres
• Managing Heroku Postgres using the CLI
• Understanding Heroku Postgres Log Statements and Common Errors