Distributed traces need to be added to ServiceBus extension

[alrod]

CRI

[nordvall]

I guess this is the same issue as I just discovered:

When sending a ServiceBus message from a ASP.NET Core application, using the Azure.Messaging.ServiceBus client version 7.5.0, the message gets a "Diagnostic-Id" header that is derived from Activity.Current in the sending process.

However, when receiving the same message with ServiceBusTrigger from ServiceBus extension v. 5.1.0, Activity.Current inside the Azure Function is totally unrelated to the diagnostic id in the incoming message (and Activity.Current.Parent is null). I expected the Activity ID inside the Azure Function to be based on the incoming ID from the message.

The above scenario works as I would expect when you call an Azure Function via the HttpTrigger. Then Activity.Current inside the Azure Function seems to be derived from the incoming http header "traceparent".

Please correct if what I am describing is unrelated to this issue.

[JoshLove-msft]

The issue here appears to be related to microsoft/ApplicationInsights-dotnet#2151. Once this issue is addressed, the end-to-end tracing should work in the function.

[azure-sdk]

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Service Bus:0.41272017,Extensions:0.18520135,Azure.Identity:0.06257013'

[jsquire]

As Josh mentioned, this issue is external to the Service Bus extension and is being tracked by AppInsights in #2151. Closing this out as a duplicate.