OpenTelemetry Java Baggage: Unenforced 32‑Item Limit in HTTP Headers

Answer

The OpenTelemetry Java SDK does not enforce a hard 32‑item limit on baggage when propagating spans over HTTP. All baggage entries present in the current context are serialized by the W3C Baggage propagator and injected into the outgoing request header without any item‑count truncation.

Confirmed facts

• The Java SDK’s io.opentelemetry.sdk.trace.propagation.W3CBaggagePropagator iterates over the baggage map and writes each key‑value pair to the header.
• No SDK configuration property (e.g., otel.baggage.max-items or otel.baggage.max-header-size) exists to set a maximum item count or header size threshold.
• The OpenTelemetry specification lists 32 items as a recommendation for interoperability and to keep the header under typical proxy limits (~8 KB).

Likely explanation

The SDK treats the 32‑item guideline as an operational target rather than a mandatory rule, relying on the underlying HTTP transport or infrastructure to provide back‑pressure when the header grows too large. This approach keeps the propagator simple and avoids imposing a hard cutoff that could break legitimate use cases.

Steps to verify the current behavior

1. Create a span and attach a baggage context with more than 32 entries (e.g., 40 unique key‑value pairs).
2. Start an HTTP client request (e.g., using java.net.HttpURLConnection or OpenTelemetry instrumentation) that will propagate the context.
3. Capture the outgoing baggage header (via a proxy, mock server, or logging interceptor) and measure its length or count of comma‑separated pairs.
4. Observe that the header contains all 40 entries and that its size exceeds the 8 KB guideline if the values are sufficiently large.

Missing diagnostic detail

If you observe header truncation or dropped baggage items in your deployment, the determining factor is the actual maximum header size enforced by your proxies, load balancers, or web servers. Knowing that limit would decide whether you need to enforce a lower baggage count in the SDK or adjust your infrastructure. Please provide the observed header size limit (or the proxy’s configured limit) so the recommendation can be tailored.