Diagnostics is not setting the Activity ParentId for OpenTelemetry tracing

[rineshpk]

Library name and version

Azure.Messaging.ServiceBus 7.9.0

Query/Question

When receiving a message through the Azure Service Bus, the parent id for the current activity is null and I could see the id received in the metadata in the 'Diagnostic-Id' field is set as a Link for the current activity. When I export the traces, it is not producing the correct trace chain (exported as two separate traces for send and receive).

If we create one activity manually and set the 'Diagnostic-Id' to the parent id on the receiver side, exported traces chain is displayed in the correct hierarchy(send and the custom activity created at the receiver side in a single trace).

Why diagnostics extension is not setting the parent id and what is the use of Link if it's not useful in chaining the trace?

Environment

No response

[jsquire]

@lmolkova : You may have the best perspective on this. Would you be so kind as to share your thoughts?

[JoshLove-msft]

@lmolkova, is this dependent on the App Insights fix here - microsoft/ApplicationInsights-dotnet#2593?
How would customers consume the fix?

[rineshpk]

@JoshLove-msft I don't think it depends on App Insight fix as I'm not using App Insight here. I've integrated OpenTelemetry/ActivitySource (as in described here ) and exported the traces to Jaeger.

[lmolkova]

@rineshpk

Links is OpenTelemetry concept that allows connecting spans without introducing parent-child relationship between them. This is necessary in batching scenarios - they're recommended by OTel messaging spec.

Jaeger supports links to some extent - you should be able to see linked traces when looking into consumer (processing) spans:

[rineshpk]

@lmolkova Thank you! Yes, I’m able see the reference link in Jaeger. But, my use case is something different and I would like to see the message send/receive in a single trace (as in the case of setting the Diagnostic-Id as parentId).

And, I could see the MessagingDiagnosticExtension class in the deprecated Microsoft.Azure.ServiceBus package was setting the Diagnostic-Id to the parentId.

Is there a way to accomplish this parent-child relationship with Azure.Messaging.ServiceBus instrumentation or is this something not supported anymore?