Performance & Scaling
Bug Report
Our traces stopped at the Kafka producer: propagating OpenTelemetry context through message headers
Every trace for an order ended at the publish step, and the consumer's work appeared as separate, unrelated traces. Our Kafka client was not instrumented, so no traceparent header was written, and the consumer started new root spans. How we injected and extracted context in headers and linked batch consumers correctly.