Performance, Tracing & APM

Performance page

Per route/job: p50 / p75 / p95 / p99, average and max duration, throughput (TPM), failure rate and Apdex. Route names are normalized (/user/123 → /user/:id) so endpoints group.

Traces & the waterfall

The Trace Explorer searches across traces; each trace renders as a waterfall with the real span tree (children nested under parents), a time ruler, op-colored bars, red bars for failed spans, and cross-service stitching by trace id.

Automatic performance issues

• N+1 Query — the same parameterized db/cache statement repeated ≥5× in one transaction (duration-gated to skip trivial repeats).
• N+1 API Call — repeated outbound HTTP to the same templated endpoint (ids collapse: /users/:id).
• Slow DB Query — a single db span over ~1s.
• Each files a Performance issue with Span Evidence: transaction, operation, the repeated query (syntax-highlighted), repeat count, total duration and estimated time saved — plus an example trace with the offending spans highlighted.

Insights & Web Vitals

Insights aggregates spans into modules — DB queries, HTTP requests, caches (hit rate), queues, mobile vitals — ranked by time spent. Browser SDKs feed Web Vitals (LCP/CLS/INP/FCP/TTFB) with good/poor thresholds.