Baggage, in OpenTelemetry, is key-value data passed along with a request between services so that they can share context. For example, a user tier or a request origin set at the entry point can be read by every service the request later passes through, without each service having to look it up again. It travels with the request, typically in headers.

It is useful for attaching business context to telemetry across a whole request path, so that data from different services can be grouped or filtered by the same attribute.

Baggage has important cautions. It is sent to every service the request reaches, including third-party services if headers are forwarded, so sensitive data should not be placed in it. It adds to the size of request headers, so keep it small. It is also not automatically added to spans or logs, so services need to read it and record it where they want it.

To use it safely, limit it to a few small, non-sensitive values, document which keys exist and who sets them, strip it at trust boundaries where requests leave your systems and check how your instrumentation handles it.