1. Event schema
One row in api_requests, with the types used by the query made explicit.
- timestamp_utc
- Timestamp
- route_template
- Utf8
- status_code
- Int64
- latency_ms
- Float64
How it works
How to set it up
1
Inspect samples first
Confirm that fields contain the expected values and types before aggregating them. This catches instrumentation mistakes early.
2
Choose what to measure
Select an aggregation, numeric field, time bucket, and filters. The newest time bucket may still be receiving events.
3
Save the chart
Save charts you check regularly to a dashboard, or use them to create alerts. Open Query when you need multiple tables or CTEs.
Exploring structured events
Inspect event samples, apply filters, and chart the results in Explore.
Boundaries
What this does not replace
- Explore works with one table at a time. Use Query for joins, multiple CTEs, and reusable SQL.
- A chart cannot compensate for incomplete instrumentation, mixed units, or unstable route and event names.
- Filter by individual identifiers when investigating an event. Grouping a chart by thousands of identifiers makes it hard to read.
Try the example
Read the schema, SQL, and sample result
This example includes the schema, read-only SQL, and synthetic results. Use it to check how the query works. It does not measure customer results.
2. Read-only SQL
Which API routes have the highest 5xx error rate with at least 20 requests?
SELECT
route_template,
COUNT(*) AS requests,
SUM(CASE WHEN status_code >= 500 THEN 1 ELSE 0 END) AS errors,
100.0 * SUM(CASE WHEN status_code >= 500 THEN 1 ELSE 0 END)
/ NULLIF(COUNT(*), 0) AS error_rate_pct
FROM api_requests
WHERE timestamp_utc >= now() - INTERVAL '24 hours'
GROUP BY route_template
HAVING COUNT(*) >= 20
ORDER BY error_rate_pct DESC
LIMIT 10;3. Synthetic result
Checkout failed on 5 of 25 requests. Search failed on 1 of 25.
| route_template | requests | errors |
|---|---|---|
| /api/checkout | 25 | 5 |
| /api/search | 25 | 1 |
| /api/profile | 20 | 0 |
Capabilities
What is included
Samples and table views for raw event inspection
Line, bar, and stacked-area charts
Count, sum, average, min, max, and percentile aggregations
Time ranges, nested-field filters, split series, and explicit columns
Add-to-dashboard and create-alert actions from results
See the analysis
SQL recipes that use this capability
Calculate API error rate by route
Rank API routes by 5xx error rate. Exclude routes with fewer than 20 requests so one failure does not dominate the results.
Open recipeMeasure background job retry and failure rate
Find unreliable jobs by comparing successful runs, retries, failures, and tail duration.
Open recipeCalculate LLM cost by feature and model
Attribute model spend, tokens, request volume, and cost per request to product features.
Open recipeCustomer evidence
How teams use this workflow
"Telemetry is one of the easiest ways to go from dumping in your data to actually understanding it."
Shayan Taslim, LogSnag
Read the customer story"Telemetry makes it super easy to track, analyze, and visualize what's going on in my business. It's the perfect mix of simple and powerful."
Namu Kang, Browserflow
Read the customer storyRelated capabilities
Related guides and examples
Start with one production workflow
Use a focused prompt, send synthetic events, and verify the first useful query before expanding coverage.