Fix span linking for Azure ServiceBus #2474
Open
+6
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Align span ID with activity's span ID in ServiceBus listener
The code changes in the
AzureMessagingServiceBusDiagnosticListener.cs
file within theElastic.Apm.Azure.ServiceBus
namespace involve modifications to how spans are started for message actions. Specifically, theStartSpanInternal
method now includes an explicitid
parameter set toactivity.SpanId.ToString()
. This change ensures that the span ID matches the activity's span ID, which is crucial for correctly linking the consuming span to the producer. This adjustment is necessary because the Azure SDK automatically attaches thediagnostic-id
andtraceparent
to the message, and proper span linking on the receiver end depends on this alignment.