How it's possible set (predefine) dd.trace_id in datadog exporter in opentelemetry-collector with another trace_id getting from backend per datadog ?

[matthiashaasesourceforge]

Hello,

my setup:

webapp -> special-backend-app

webapp use datadog-agent with trace_id (all incl. per datadog-agent)
special-backend-app can only use opentelemetry-collector per docker-compose.yml incl. otel-collector.yml

problem:

otel-collector. gets "special traces" from special-backend-app.

These "special traces" includes a attribute/field like messaging.datadog_trace_id

i can set(/preset/change) the otel inline per otel-collector.yml line:

...
transform:
error_mode: ignore
trace_statements:
- context: span
statements:
- set(attributes["otel.trace_id"],attributes["messaging.datadog_trace_id"])
where attributes["messaging.datadog_trace_id"] != nil
...

hint:
But i can not do: set(attributes["dd.trace_id"].
Or better i can do, but it does not make any effect.

datadog exporter takes the trace but defines/creates his own trace_id .

At the end i can not see all traces together correct with one trace_id in datadog.

The webapp trace and special-backend-app trace are alone and not connected per spanview .
Each service has his own line.
Nothing shown together.
trace_id's are not the same. :(

question:
Is there any solution how i can predefine dd.trace_id and take datadogexporter ?

Regards
Matthias

[matthiashaasesourceforge]

No answer ?

[matthiashaasesourceforge]

Nobody had the same problem ?
Nice opensource support ...