We have a similar case, but it can't be fixed with the X-Dynatrace header since the NServiceBus handlers are defined as custom services (listeners) and do't start with an HTTP call. No Http, no headers, no linked purepaths.
I know we can solve this by using the DT SDK: https://github.com/Dynatrace/OneAgent-SDK-for-dotnet#trace-messaging
But can this also be achieved via OpenTelemetry? Since that's an open standard it would make more sense to us.
I believe so, there's a trace ingest endpoint that you can use: https://www.dynatrace.com/support/help/how-to-use-dynatrace/transactions-and-services/purepath-distr...
I know about that one and even used it already, but in this case I don't need to ingest because I have Dynatrace OneAgent at both ends. It's just a matter of stitching purepaths. Which is documented via the oneagent SDK, but I don't know how to do it via OpenTelemetry for dotNet.