Request IDs, tracing and safe logs

Follow a request across layers.

UnderstandStudy an examplePractise

Understand the concept

Request IDs correlate logs; distributed traces connect calls across services. W3C traceparent carries standard context, not trusted user identity or permission. Validate externally supplied identifiers and sizes.

Monitor statuses, latency distributions, timeouts, transfer size and downstream failures together. Averages hide tails; interpret p95/p99 with sample size. Business failures hidden under 200 can mislead alerts.

Redact credentials, cookies, personal bodies and query secrets. Public correlation IDs can locate protected diagnostics without exposing stacks or SQL. Timing fields can help diagnosis but should not reveal unnecessary internal topology.

WHEN TO USE IT

Find the right production request and failure.

COMMON PITFALL

Logging every field and body without redaction.

01 / PRACTICE

One topic. Three levels of depth.

HTTP / illustrative example

traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01

An illustrative W3C context, not an identity token.

This page does not send requests to external servers. Messages are readable HTTP/1.1 illustrations, not HTTP/2 or HTTP/3 wire dumps. example.test is reserved for examples. Run commands and JavaScript only in your own test environment; never publish real tokens or cookies.

02 / YOUR TURN

Try it yourself first.

Should an error report log Authorization?

Show the solution and explanation

Worked solution

Redact credentials; retain safe correlation

No; preserve safe correlation instead of credentials.

RasimAtaberkŞahin

Understand the concept

One topic. Three levels of depth.

Try it yourself first.