Living note

Tracing a Request End to End

A compact mental model for following one request through browser, edge, application, and storage layers.

When latency rises, a shared request map is more useful than a collection of isolated dashboards.

The path

Start with the user-visible event and follow the same trace identifier across every boundary.

  1. Browser navigation and DNS resolution
  2. TLS, CDN, and edge routing
  3. Application work and downstream calls
  4. Response streaming and client rendering

A useful trace