Telemetry
Shared dashboards

Keep operational and product signals readable in one shared view

Combine Explore results, SQL query charts, result tables, section headers, and explanatory notes into dashboards that coding agents can seed and humans can refine.

Outcomes

  • Give engineering, product, support, and founders a common view of the workflow.
  • Put definitions and operating notes next to the charts they explain.
  • Create or update dashboards through the API when automation owns the first pass.

How it works

A reviewable workflow from signal to decision

1

Lead with the decision

A dashboard should answer a small set of related questions. Start with the primary health or outcome metric rather than every available chart.

2

Place diagnosis after detection

Put trend and threshold views first, then add breakdowns and recent-event tables that explain a change.

3

Document ownership and response

Use headers and notes to define the metric, expected range, owner, and next step. Context makes the dashboard usable during an incident.

Capabilities

What is included

Explore and SQL query widgets
Line, bar, scatter, stacked-area, and table results
Section headings and markdown notes for context
Drag, resize, rename, and share team-scoped dashboards
Dashboard create, update, list, and delete API

See the analysis

SQL recipes that use this capability

Start with one production workflow

Use a focused prompt, send synthetic events, and verify the first useful query before expanding coverage.

Open prompt pack