Protocols
Saved & recent

Correlation ID

Also called: request ID, trace ID, request correlation

A correlation ID connects messages or records belonging to the same exchange or operation. A request/response protocol may echo a request ID; a distributed tracing system propagates trace context across services. The identifier’s meaning and propagation rules are part of the chosen protocol or application convention.

A checkout request passing through an API, inventory service and payment service can keep one trace ID while individual spans receive different IDs. Engineers can then find the related records together. A correlation identifier is not an authorization credential or an idempotency key: matching two records does not permit access or suppress duplicate effects.

Related
JSON-RPC, Idempotency key, HTTP headers
Further reading
W3C — Trace Context
T7 T7 API T7 S1 T7 · S1 Inventory T7 S2 T7 · S2 Payment T7 S3 T7 · S3 logs grouped by trace T7 abbreviated identifiers
A shared trace ID links related work while separate span IDs distinguish operations. The labels are schematic abbreviations.

View in the full Protocols collection