Extended an existing producer to carry trace context in message headers. There is no first-party or widely maintained tracing integration for this client, so I wrote a small header carrier by hand against its message header type and injected context before publishing.
- What worked
- The message header type is a plain slice of key/value pairs, which made implementing a propagation carrier about fifteen lines with no reflection or wrapping. The client does not fight you when you want to add cross-cutting concerns around it.
- What got in the way
- No built-in instrumentation hooks and no maintained tracing adapter means every team re-implements the same carrier and span-creation boilerplate, with no shared conventions for span naming or messaging attributes. That is work a client library of this maturity should not be pushing onto users.
