Event contract
Fields the query expects
| Field | Type | Why it exists |
|---|---|---|
| timestamp_utc | Timestamp | Navigation completion time. |
| destination_route | Utf8 | Stable destination route template. |
| release | Utf8 | Frontend release identifier. |
| duration_ms | Float64 | Time from navigation start to ready state. |
| status | Utf8 | success, failed, or abandoned. |
Copy the query
SELECT
destination_route,
release,
COUNT(*) AS navigations,
approx_percentile_cont(duration_ms, 0.50) AS p50_ms,
approx_percentile_cont(duration_ms, 0.95) AS p95_ms,
100.0 * SUM(CASE WHEN status <> 'success' THEN 1 ELSE 0 END)
/ NULLIF(COUNT(*), 0) AS unsuccessful_pct
FROM frontend_navigation_events
WHERE timestamp_utc >= now() - INTERVAL '7 days'
GROUP BY destination_route, release
HAVING COUNT(*) >= 50
ORDER BY p95_ms DESC;This read-only query is planned and executed against an empty typed table with Apache DataFusion 45.2.0. The deterministic sample output is synthetic and reviewed separately; validate field types, thresholds, and business definitions against your own data. Read the testing methodology.
Query result
p95 client navigation latency
Report navigation has a much wider tail and a higher unsuccessful share.
| destination_route | release | navigations | p50_ms | p95_ms | unsuccessful_pct |
|---|---|---|---|---|---|
| /reports/:id | web-103 | 640 | 780 | 3,210 | 3.13 |
| /projects/:id | web-103 | 1,820 | 410 | 1,480 | 1.21 |
Synthetic example output. Run the query against your own event schema and thresholds before using it for operational decisions.
Reproduce the example
Download the public fixture
The JSON bundle includes the typed event contract, illustrative input rows, exact SQL, expected output, review notes, and engine version. The CSV contains the displayed result.
How the SQL works
- 1The completion boundary should represent a route-specific ready state rather than only a URL change.
- 2p50 and p95 distinguish a generally slow route from an intermittent long tail.
- 3Failed and abandoned navigation stays beside latency so fast failures cannot make performance look healthy.
Edge cases to decide
- Prefetching changes the work included in duration.
- Background tabs distort browser timing and should be categorized.
- Use route templates instead of identifiers or query strings.
Recommended dashboard
- Grouped bars: p50_ms and p95_ms by route
- Trend: p95_ms by release
- Table: slowest safe navigation samples
Alert guidance
Alert when a high-volume route exceeds its reviewed p95 objective for complete buckets.
Read alert setupPut the recipe to work
Related instrumentation and guides
Continue the analysis
Compare Core Web Vitals by Route and Release
Compare LCP, INP, and CLS samples by stable route and release while keeping the percentage of passing samples visible.
Open recipeRank JavaScript Errors by Route and Release
Find frontend releases and routes with the most repeated JavaScript failures and affected sessions.
Open recipeCalculate Browser Long-Task Rate by Route
Measure main-thread blocking events and their total blocked time by route and frontend release.
Open recipeRun it on real events
Create a table, adapt the fields, and save the result
Start free, send structured events, and use the query result as a chart, shared dashboard widget, or alert input.