Accept and issue OpenTelemetry/W3C style trace context (traceparent header) about beeline-python

[irvingpop]

Agreed! In fact, we're planning to add this to the Beelines. It's a slower effort for us because we need to think about feature parity in all the language implementations.

Here' a summary of our intent:

We will be modifying each of the official beelines, as well as some of our agents to do the following:

• Automatically parse Honeycomb and W3C TraceContext headers included in incoming requests. If both header formats are present, the Honeycomb headers will be given precedence. Other header formats can be parsed with a callback function specified in the Beeline initialization (see example code).
• Outgoing HTTP requests will be instrumented according to a callback function specified in the Beeline initialization. This will allow users of beelines to make decisions about whether to instrument the outgoing request, or not (i.e. to avoid data leakage when making outbound calls to 3rd party APIs).

hey @paulosman @martin308 if @garthk contributed a PR along those lines would you be open to it, or do you already have an implementation you're rolling with?

[paulosman]

Thanks for the mention. Yup, this is on our roadmap and we're actively working on it! I'd avoid a PR to prevent duplicate work, but this issue will be mentioned when we have something ready to look at.

[JamieDanielson]

Sorry for the delayed response! This has since been added - see our docs for more details as needed.

#116 generates W3C-compliant headers, #122 and #123 adds parser and propagation hooks, and #199 detects incoming W3C headers and parses automatically. 🎉