Skip to content
Telemetry
Dashboard examples

SaaS dashboards with SQL and sample results

Choose a question you need to answer. Each example includes the event schema, SQL, sample results, and notes on what the numbers mean. Open its page to review or share it.

Reviewed by the Telemetry product team on . We checked what each dashboard counts, metric definitions, SQL syntax, sample results, and how data freshness affects interpretation. Who reviews this page

6

dashboard examples

24

named metric definitions

100%

SQL visible before signup

Choose a dashboard question

Start with the dashboard audience and question

The previews use synthetic data to show how to arrange the charts. They do not measure customer results or Telemetry performance.

Founders, product leaders, and engineering leadersDaily, after the newest complete UTC day

SaaS health overview

Compare account activity, API errors, and revenue on one dashboard. Aggregate each table by account before joining it.

Did account adoption, application reliability, or represented revenue change enough to require a deeper review?

  • Active accounts
  • Successful milestones
  • API error rate
  • Monthly revenue represented
Read the schema, SQL, and assumptions
Service owners and on-call engineersFive-minute buckets for operations; daily for reviews

API reliability and latency

Compare traffic, error rate, and tail latency by endpoint while retaining enough volume to judge whether a percentile is stable.

Which endpoints have rising error rates or p95 latency, and enough requests to trust the comparison?

  • Request volume
  • Error rate
  • p50 latency
  • p95 latency
Read the schema, SQL, and assumptions
Incident commanders and customer-facing teamsDuring an incident and once after resolution

Incident customer impact

Translate a declared service incident into affected accounts, failed operations, regions, and represented revenue.

Which accounts and operations were directly represented in a declared incident window?

  • Affected accounts
  • Failed operations
  • Affected regions
  • Represented monthly revenue
Read the schema, SQL, and assumptions
AI product, platform, and finance teamsDaily with a complete provider-cost window

LLM usage and unit economics

Attach workflow and account identifiers to model calls. Compare their token usage, latency, failures, and cost.

Which model-backed workflow consumes the most estimated cost per successful outcome?

  • Requests
  • Input and output tokens
  • Estimated cost
  • Cost per successful request
Read the schema, SQL, and assumptions
Async platform and application teamsHourly for operations; weekly for capacity planning

Background job reliability

Separate final job outcomes from attempts, then compare retries, queue wait, and duration by stable job name.

Which logical job types fail permanently, retry, wait, or run slowly?

  • Completed jobs
  • Terminal failure rate
  • Retry rate
  • p95 duration
Read the schema, SQL, and assumptions
Product managers and growth engineersDaily, segmented by signup cohort

Account activation funnel

Count completed account milestones in order. Show how many accounts were eligible for each step.

Which activation step loses the most new accounts?

  • Signed-up accounts
  • Sources connected
  • First queries run
  • Dashboards created
Read the schema, SQL, and assumptions

Run the same analysis on a connected sample database

The SQL Lab includes product, API, model, job, billing, release, and incident data with more than 10,000 deterministic rows. Download it or query it locally before mapping these dashboards to production fields.

Open the SQL LabChoose an event contractDashboard design guide