Dashboards
Dashboards put business numbers and operational health on the same canvas. A widget can read from a saved query, a monitor, a host, or a metric — so the KPI and the uptime of the service producing it live side by side.
- Read
- 5 min
- Module
- Dashboards
Widget sources
Every widget declares a source. They all resolve through one endpoint, so the chart renderers do not care where the numbers came from — which is what lets a single dashboard mix a revenue query with the uptime of the checkout endpoint.
Widget types
| Type | Best for | Shape expected |
|---|---|---|
| Line / area | A value over time | One time column + one or more numeric columns |
| Bar | Comparison across categories | One label column + one numeric column |
| Stat | A single headline number | First row, first numeric column |
| Table | Detail you actually read row by row | Any result set |
| Uptime | Availability of a monitor | Monitor source only |
Layout and refresh
Widgets sit on a grid you drag and resize; the layout is versioned, so an older client cannot corrupt a newer arrangement. Each widget carries its own refresh interval — a monitor tile can poll every 30 seconds while an expensive nightly aggregation refreshes once an hour.
Sharing and embedding
A dashboard can be shared read-only through a signed public link, or embedded in another product using a workspace embed key. Both paths are scoped to the single dashboard and carry no session — a shared link cannot be walked back into the console.