[BUG]: new baggage propagator default breaks existing tracing

[chadawagner]

Tracer Version(s)

1.73.0,1.73.1

Go Version(s)

go version go1.23.1 darwin/arm64

Bug Report

The propagation styles default was previously "datadog,tracecontext" but was changed in v1.73.0 to "datadog,tracecontext,baggage".

As the chained propagator tries the configured options, if nothing is found for the first 2, and if any unrelated baggage headers are present in the incoming request (e.g. "Baggage: foo=bar"), it will somehow consider that a valid span context and we end up with a span in the context with a trace ID of 0, rather than a new trace ID being generated.

We can avoid this issue by setting the propagation styles back to "datadog,tracecontext". But it seems like the correct behavior would be if baggage is found but contains no span context data then it should be considered "span context not found" and a new span context should be created.

Reproduction Code

No response

Error Logs

No response

Go Env Output

No response

[mtoffl01]

Hi @chadawagner ,
Thanks for reaching out. We are in the process of fixing this. We will update you once the fix is complete. We apologize for the inconvenience.