How to propagate across Sentry Instrumented to Otel instrumented services?

[ckblockit]

Problem Statement

I have
a) a web server (NodeJS + Express) which instruments Sentry SDK.
b) a service running with public Docker image that instruments OTEL with its own SDK

(a) Web server calls (b) service via HTTP request.

I am exporting the trace from the b) to sentry using Otel Collector, but it doesn't show up in Sentry as part of the same trace (not showing up at all)

Solution Brainstorm

Can you simply update the propagator to always add W3C header?
I believe NodeJS package doesn't do this based on the documentation?

Additional Context

I am not sure why this is not implemented by default.
What's the harm on enabling this propagateTraceparent option true by default for all pakcages?

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1592

[Lms24]

Hi @ckblockit thanks for writing in!

What's the harm on enabling this propagateTraceparent option true by default for all pakcages?

All platforms supporting CORS (browser, mobile SDKs building on top of our browser SDKs) would block requests if we attach the traceparent header by default. This is quite an annoying breaking change for users, as we learned, when we started propagating the baggage header in v7 of the SDKs. Not an issue for your use case but something we have to keep in mind.

Since 10.31.0, the Node SDK supports optionally sending the W3C traceparent header along, if you set propagateTraceparent: true in your SDK init call. Can you let me know if this works for you?