Skip to main content
Tip: Make sure you have completed the Heroku setup and have a working Heroku Log Drain (for Cedar generation) or Heroku Telemetry drain (for Fir generation) before continuing with this section.
These dashboards are created automatically as Intelligence dashboards when a Log Drain or Telemetry Drain is set up. No further action is required. Which dashboards appear depends on the Heroku generation and add-on plans you use:

​
Status code dashboard

This dashboard is available only for Heroku Cedar generation applications.
The Heroku Status dashboard aggregates the status codes returned by Heroku into the main categories (2xx, 3xx, 4xx and 5xx). One graph shows the count per category, and a second graph shows each category as a percentage of all requests.

​
Redis dashboard

For Heroku Cedar generation, Redis metrics are available on premium (or higher plan) instances. For Heroku Fir generation, Redis metrics are available on all instances.
The Heroku Redis dashboard is based on the metrics provided by Heroku. It shows active connections, hit rate, evicted keys and Redis host metrics. Active connections: The number of connections established on the Redis instance. Hit rate: The ratio of successful reads out of all read operations, rounded to five decimal points. Evicted keys: The number of evicted keys due to reaching your instance maxmemory limit. Memory: Approximate amount of memory used by your Redis processes in kB. This includes shared buffer cache as well as memory for each connection. Server load average: Average load on the system over a period of 1 minute. Server I/O: Number of read/write operations in I/O sizes of 16KB blocks. Server memory: Memory on the Redis server, split into in use, free, and cached.

​
PostgreSQL dashboard

This dashboard is available only for Heroku Postgres Standard and Premium instances.
The Heroku Postgres dashboard is based on the metrics provided by the Heroku platform and it shows database size, connections and index hit rates. Database Size: The number of bytes contained in the database. This includes all table and index data on disk, including database bloat. Tables: The number of tables in the database. Index Cache Hit Rate and Table Cache Hit Rate: Ratio of lookups served from the shared buffer cache, rounded to five decimal points. Heroku recommends a value of 0.98 or greater. If it drops below 0.98 consistently, investigate your expensive queries or upgrade your database plan for more RAM. Cache hit rate is a great metric to set an anomaly detection trigger on. Active Connections: The number of connections established on the database. Waiting Connections: Connections waiting for a lock. If there are too many connections waiting, it could point to over-use of connections by not using a connection pool, for example. Memory: Approximate amount of memory used by your database’s Postgres processes in kB. This includes shared buffer cache as well as memory for each connection. Server load average: Average system load of the Heroku database server. For more information about how to read load averages, see our blog post “Understanding system load and load averages”. Server I/O: Number of read/write operations in sizes of 16KB blocks. Each Postgres plan has a limit on IOPS it can perform (see the Heroku docs), so this is an excellent candidate to set an anomaly detection trigger on. Server memory: Memory on the database server, split into in use, free, and cached. For multi-tenant plans, server metrics may include other databases and might be misleading. WAL usage: Write Ahead Log usage, as a percentage. A healthy database has this at 0.75 or lower. Above 0.75, Heroku limits connections to the Postgres instance. Follower lag: The number of commits this follower is behind its leader. This graph is empty if there are no followers. For more information about these metrics, you can read more on the Heroku documentation page.