KorrelationsID

KorrelationsID is a unique identifier used to link together events, logs, and metrics that stem from the same user action or processing job as it moves through a system of interconnected components. Often described as a correlation or trace identifier, it provides end-to-end visibility in distributed environments where a single request touches multiple services, queues, and databases.

Propagation and usage

The KorrelationsID is typically generated at the edge of a system, such as a client, gateway, or initial service, and then propagated across all downstream components. It is carried through HTTP headers (for example, correlation-id or Korrelations-ID), message metadata, or event payloads. The identifier remains constant for the entire lifecycle of the request or transaction and should be included in logs, traces, and metrics to enable cross-service correlation.

Generation and lifecycle

A KorrelationsID should be globally unique and resilient to retries or partial failures. It can be a UUID or another structured format, designed to withstand long-chain propagation. Best practices include avoiding embedding sensitive data in the ID, ensuring consistent propagation across all channels, and not reusing IDs for unrelated requests. The ID may be logged at each step and can be used to stitch together distributed traces or root-cause analyses.

Relation to tracing

While dedicated tracing systems use structured fields like trace-id and span-id, a KorrelationsID serves as a lightweight linkage mechanism. It can complement full tracing by enabling log-based correlation when a full trace context is unavailable or impractical. Operators often maintain both a KorrelationsID and, where possible, a richer tracing context to improve observability.