Question About Trace Flag Propagation in UnmarshalHoneyCombTraceContext and MarshalW3CTraceContext

[Flgado]

Hi team,

I am trying to propagate tracing information from the Honeycomb header using UnmarshalHoneyCombTraceContext, followed by MarshalW3CTraceContext, and then passing it to OpenTelemetry (Otel).

I noticed that UnmarshalHoneyCombTraceContext correctly parses the trace_id, parent_id, and context, but it does not seem to parse or propagate the trace-flags. As a result, when MarshalW3CTraceContext processes the data, it does not receive the flag, preventing it from being forwarded to OpenTelemetry. Since OpenTelemetry relies on this flag, if using the default trace sampling, to determine whether a request should be traced, this behavior raises some questions.

Is this an intentional design decision, meaning that the propagation of the trace flag must be explicitly handled by developers? Or is this a missing feature in the library? Has anyone encountered this issue before?

Thanks :)