Creating Dashboards
Telemetry has native dashboards built directly into the product. You can pin visualizations from both Explore and Query, then arrange them into a single team view.
What a dashboard includes
- Dashboard: a named page for related metrics.
- Widget: a saved chart or table.
- Widget source: either an Explore configuration or a Query result/chart.
- Layout: drag and resize widgets in Edit mode.
Step 1: Create a dashboard
You can create dashboards in two ways:
- In the left sidebar, open Dashboards menu and click New Dashboard.
- From Explore, click Add to Dashboard. If no dashboards exist yet, Telemetry will prompt you to create one first.
Step 2: Add widgets from Explore
- Open a table and go to the Explore tab.
- Choose:
- graph type (
Samples,Table,Line,Bar, orStacked Area) - aggregation and granularity (for chart views)
- time range, filters, and group by fields
- graph type (
- Click Run.
- In the results toolbar above the chart, click Add to Dashboard.
- Enter a widget title, select a dashboard, and save.
After you run an Explore query, Telemetry shows the action buttons on the right side of the results toolbar:

Use Add to Dashboard from the results toolbar after clicking Run.
Telemetry stores the full Explore state, so the widget stays consistent with the chart/table you pinned.
Step 3: Add widgets from Query
- Open a saved query or draft query.
- Run the query and switch to either Results or Chart.
- Click Add to Dashboard.
- Choose the destination dashboard and save.
Use this path when you want fully custom SQL rather than Explore-generated SQL.
Step 4: Arrange and maintain your dashboard
- Open
/team/{team}/dashboard/{dashboard-slug}. - Click Edit.
- Drag widgets by the handle, resize as needed, and remove widgets with
X. - Click Done when layout changes look right.
You can also rename, copy URL, or delete dashboards from the dashboard actions menu in the sidebar.
Inline interactive examples
Example 1: Error rate trend widget (Line)
Run this in Explore or Query, then pin it with Add to Dashboard.
SELECT
date_trunc('hour', timestamp_utc) AS hour,
100.0 * SUM(CASE WHEN status_code >= 500 THEN 1 ELSE 0 END) / COUNT(*) AS error_rate_pct
FROM
http_logs
WHERE
timestamp_utc >= now() - INTERVAL '7 days'
GROUP BY
hour
ORDER BY
hour ASC
Example 2: Top slow endpoints widget (Bar)
Use a Bar chart for ranking. Great for API and queue monitoring dashboards.
SELECT
endpoint,
AVG(duration_ms) AS avg_duration_ms
FROM
http_logs
WHERE
timestamp_utc >= now() - INTERVAL '24 hours'
GROUP BY
endpoint
ORDER BY
avg_duration_ms DESC
LIMIT 15
Example 3: Recent failures drilldown widget (Table)
Add this as a table widget next to trend charts for fast root-cause debugging.
SELECT
timestamp_utc,
service,
endpoint,
status_code,
error_message
FROM
http_logs
WHERE
status_code >= 500
AND timestamp_utc >= now() - INTERVAL '24 hours'
ORDER BY
timestamp_utc DESC
LIMIT 200
Dashboard design tips
- Keep one primary question per widget (for example: "Are error rates rising?").
- Mix trend widgets with drilldown tables.
- Use clear widget titles so teammates can scan the page quickly.
- Start with 4-8 widgets; add more only when each one adds a new decision signal.