Broken trace context propagation: OTel Trace ID
of DD agent spans converted by OTel Col Datadog Receiver are wrong
#36926
Labels
Trace ID
of DD agent spans converted by OTel Col Datadog Receiver are wrong
#36926
Component(s)
receiver/datadog
What happened?
Description
When doing W3C Trace Context Propagation from an app instrumented with OTel to an app instrumented with the Datadog agent and the Datadog agent sending spans to the OTel Collector Datadog Receiver, the Trace Id reported by the OTel Collector Datadog
Receiver is different from the Trace ID of the parent spans, breaking the trace.
I can't confirm but I suspect that this is caused by the logic in the OTel Col Datadog
Receiver to produce the OTel Trace ID from the Datadog ids.
Architecture:
OTel Collector debug log.
traceId=37940834c74a2dfc11835c979eca1433
spanId=bb4331d223d59950
parentId=bb4331d223d59950
as expectedtraceId=000000000000000011835c979eca1433
which is NOT expected, we expect37940834c74a2dfc11835c979eca1433
Steps to Reproduce
traceparent
http header to verify the context is propagatedExpected Result
traceID
and theparentId
of the HTTP handler of the "downstream_app" matches thespanId
of th HTTP call of the "upstream_App".Actual Result
The
parentId
is properly propagated by theTraceId
is wrong.Collector version
v0.116.0
Environment information
Environment
MacOS 15.2
Demo app:
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: