Gerhard Stöbich

seems this is caused by either the application installs two OTel instances (one via applicationinsights => @azure/monitor-opentelemetry) or applicationinsights does something wrong. I guess it's better to ask the azure...

Maybe don't register the `W3CBaggagePropagator`? But this is not limited to HTTP, would also effect GRPC,...

You can manually specify the propagators you want during calling register. e.g. ```js const provider = new NodeTracerProvider(); provider.register({ propagator: new W3CTraceContextPropagator() }); ``` It should also work to set...

> I actually want to block incoming baggage but push some baggage outbound so I dont want to completely disable the propagator but I could make the extract function a...

There is an "ongoing" discussion in API spec regarding this: see https://github.com/open-telemetry/opentelemetry-specification/issues/530 and https://github.com/open-telemetry/opentelemetry-specification/pull/3103 I fear as long as spec part is not finished it's hard to get this into...

Not sure if this behavior should be the default. Note that spans are only exported once they are ended, at least with most exporters (e.g. OTLP, Jaeager, zipkin). So you...

What is missing in your code is the `enable()` call of `ZoneContextManager` so try `contextManager: new ZoneContextManager().enable(),`. As said I'm not familiar with web and which context is use where...

@dyladan see `AlwaysSameContextManager.theContext = trace.setSpan(ROOT_CONTEXT, span);` to set the one and only parent. But as written this includes propagators so a bit more is needed.

@AkselAllas Sorry but I don't understand your question. What else is missing besides the hacky `AlwaysSameContextManager` I sketched above to move forward?

Actually there is no need to wait with instrumentation creation until SDK has finished resource detection (see https://github.com/open-telemetry/opentelemetry-js/issues/3146). So maybe we should fix this instead of documenting the bug.