Manually propagating a distributed tracing context from third party http client (.net)

[Nicolas_Rey]

Hello @trentm and @Wolfgang_Ziegler

We finally found the problem, nothing related to Elastic APM : we also use Dynatrace with the http headers trace enabled

As we supposed, the headers may be overridden by Dynatrace with ids from it's own context. When disabling the option, the behavior has gone.

Thanks for your time, I hope it could help people facing the same situation