Event schema

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.

DataFusion SQL

Copy the query

sql

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. We review the synthetic sample output separately. Check field types, thresholds, and counting rules 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.

Compare a numeric result field

/reports/:id

3,210 ms

comparison 780 ms

/projects/:id

1,480 ms

comparison 410 ms

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.

p95 client navigation latency: static chart of synthetic p95_ms values from the Measure SPA navigation latency by route example result — Download this SVG chart of the sample results for an article, runbook, or design review. Please credit Telemetry.

Reproduce the example

Download the sample data

The JSON bundle includes the event schema with field types, illustrative input rows, exact SQL, expected output, review notes, and engine version. The CSV contains the displayed result.

Sample JSON Expected output CSV Static SVG chart

How the SQL works

1Record completion when the route is ready to use. A URL change alone does not mean the page has finished loading.
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 check

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 setup

Set up the events this query needs

Related instrumentation and guides

Frontend performance monitoring Core Web Vitals by release Explore product

Continue the analysis

Run it on your 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.

Get an API key

Measure SPA navigation latency by route