|
| 1 | +# Render automated dashboards |
| 2 | + |
| 3 | +[Render](https://render.com/) is a cloud platform-as-a-service for running web services, background workers, persistent disks, Postgres databases and Key Value (Valkey/Redis) instances. |
| 4 | + |
| 5 | +These dashboards display data emitted by Render's [OpenTelemetry metrics stream](https://render.com/docs/metrics-streams), forwarded to AppSignal through the AppSignal collector. The collector's Render router converts CPU, memory, disk usage, disk I/O and network I/O metrics into host metrics; the remaining `render.*` metrics are exposed as custom metrics and power these dashboards. |
| 6 | + |
| 7 | +The following automated dashboards may appear: |
| 8 | + |
| 9 | +- [HTTP automated dashboard](#http-automated-dashboard) |
| 10 | +- [Postgres automated dashboard](#postgres-automated-dashboard) |
| 11 | +- [Key Value automated dashboard](#key-value-automated-dashboard) |
| 12 | + |
| 13 | +All three dashboards are currently marked Beta. |
| 14 | + |
| 15 | +## HTTP automated dashboard |
| 16 | + |
| 17 | +The "Render/HTTP" dashboard shows request volume and latency for Render web services. Render aggregates these metrics across all instances of a service, so each line corresponds to a host/status_code combination across the whole service rather than to a specific replica. |
| 18 | + |
| 19 | +The following graphs are displayed in this automated dashboard: |
| 20 | + |
| 21 | +- HTTP requests (broken down by status code and host) |
| 22 | +- HTTP latency (p50/p95/p99 broken down by host and status code) |
| 23 | + |
| 24 | +These graphs display values from the `render.service.http.requests.total` and `render.service.http.requests.latency` metrics. |
| 25 | + |
| 26 | +## Postgres automated dashboard |
| 27 | + |
| 28 | +The "Render/Postgres" dashboard shows information about Render Postgres instances. |
| 29 | + |
| 30 | +The following graphs are displayed in this automated dashboard: |
| 31 | + |
| 32 | +- Connections (active connections per database, compared against the connection limit) |
| 33 | +- Storage size (database size and indexes size per database) |
| 34 | +- Transaction volume |
| 35 | +- Sequential table scans (per database) |
| 36 | +- Transaction exhaustion (per database) |
| 37 | +- Slow locks |
| 38 | +- Slow lock wait time |
| 39 | +- Replication lag (per replica host) |
| 40 | + |
| 41 | +These graphs display values from the `render.postgres.*` metrics. |
| 42 | + |
| 43 | +## Key Value automated dashboard |
| 44 | + |
| 45 | +The "Render/Key Value" dashboard shows connection metrics for Render Key Value (Valkey/Redis) services. CPU, memory, disk and network usage for Key Value services are reported as host metrics and appear on the host metrics dashboard instead. |
| 46 | + |
| 47 | +The following graphs are displayed in this automated dashboard: |
| 48 | + |
| 49 | +- Connections (active connections compared against the connection limit) |
| 50 | + |
| 51 | +This graph displays values from the `render.keyvalue.connections` and `render.keyvalue.connection.limit` metrics. |
0 commit comments