Menu

Automated dashboards

AppSignal automatically creates dashboards when it detects metrics from a supported integration. These automated dashboards give you pre-built charts for the most important metrics of each integration, without any manual setup.

Automated dashboards appear in the Dashboards section of your app, labeled as Automated. They are created the first time AppSignal receives metrics from a supported source. If you remove the integration or stop sending the metrics, the dashboard stays in place so you can reference historical data.

How automated dashboards work

Each integration sends specific metrics to AppSignal. When AppSignal recognizes a set of metrics that matches a known integration, it creates a dashboard with charts tailored to that integration. The charts, layout, and descriptions are maintained by AppSignal and updated automatically unless you have customized the dashboard.

Dashboards are designed to answer common operational questions quickly. Health and error indicators appear first, followed by resource utilization, then operational context. Chart descriptions explain what values indicate a problem and what to do about it.

Available automated dashboards

Automated dashboards are available for the following integrations, grouped by category. Each link leads to the integration's setup instructions and dashboard details.

AWS CloudWatch

AppSignal supports automated dashboards for over 46 AWS services through CloudWatch Metric Streams. Each AWS service gets its own dashboard with charts ordered by urgency of signal.

See AWS automated dashboards for the full list of supported services and their charts.

Ruby

The following integrations create automated dashboards when AppSignal detects their metrics in a Ruby app:

  • Active Job — job duration, job status per queue, and throughput per job class.
  • Sidekiq — worker duration, queue latency, queue length, job status, Redis memory usage, and connection counts.
  • Puma — thread pool capacity, connection backlog, and worker status.
  • MongoDB — query throughput and query duration per database.
  • Ruby VM — garbage collection counts, heap slots, allocated objects, and thread count.
  • Global VM Lock — GVL wait time and waiting thread count.
  • Action Mailer — deliveries per mailer action.
  • Karafka — consumer messages, batches, lag, errors, connections, and thread counts.

Elixir

  • Oban — job duration, queue wait time, and job counts broken down by worker, queue, and status.
  • Erlang VM — I/O, schedulers, processes, memory, atoms, and scheduler utilization.

Node.js

  • V8 heap statistics — heap size, used heap, malloced memory, and native context counts.

General

  • Process Memory — RSS memory usage per host and process type. Available for Ruby and Elixir apps.

Infrastructure

  • NGINX — request time, throughput, status codes, connections, and upstream proxy metrics.
  • Kubernetes — node and pod resource usage including CPU, memory, swap, disk, and network, across two dashboards (nodes and pods).

Heroku

Heroku creates several automated dashboards from Log Drain or Telemetry Drain data:

  • Status codes — HTTP status code breakdown (Cedar generation only).
  • Redis — connections, hit rate, evictions, memory, and I/O.
  • PostgreSQL — connections, cache hit rate, memory, load average, and I/O (Standard and Premium plans).

Vector

AppSignal creates dashboards from metrics collected through Vector sources:

  • PostgreSQL — record operations, transactions, deadlocks, and temporary file writes.
  • MongoDB — three dashboards covering status (memory, connections, operations), WiredTiger storage engine internals, and replication health.

Vercel

  • Speed Insights — Next.js Web Vitals for real-user performance monitoring.