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 will be generated automatically as “Intelligence dashboards”, when a Log Drain or Telemetry Drain is set up. No further action is required. Note that in some cases you need a:

​
Status code dashboard

This dashboard is available only for Heroku Cedar generation applications.
The status dashboard shows an aggregation of the status codes, returned by Heroku. These a grouped in the main status code categories (2xx, 3xx, 4xx and 5xx).

​
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 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. Redis hit rate: The ratio of successful reads out of all read operations, rounded to five decimal points. Redis 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. Redis server Load average: Average load on the system over a period of 1 minute. Redis server I/O: Number of read/write operations in I/O sizes of 16KB blocks

​
PostgreSQL dashboard

This dashboard is available only for Heroku Postgres Standard and Premium instances.
The Postgres dashboard is based on the metrics provided by the Heroku platform and it shows database size, connections and index hit rates. 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. Index/Table cache hit rate: Ratio of index lookups served from a buffer cache. Ideally, this value is always 0.99 or higher. If it drops below 0.99 consistently, you may need to upgrade your database plan or add more RAM. Cache hit rate is a great metric to set an anomaly detection trigger on. Memory usage: We track both memory used by Postgres and the system itself. Postgres memory includes buffer cache and memory per connection. For multi-tenant plans, system metrics may include other databases and might be misleading. Load average: Average system load of the Heroku database server, for more information about how to read load averages, we’ve written a blog post about it a while ago called: “Understanding system load and load averages”. I/O read/write operations: 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 here), this would be an excellent candidate to set an anomaly detection trigger on. For more information about these metrics, you can read more on the Heroku documentation page.