So far, no agent had distributed tracing and span link support for Azure Service Bus. .NET implemented it recently and it uses the diagnostic-id application property - as suggested in the spec.
For clarity and better compatibility across agents, this PR removes the word "possibly" - so diagnostic-id should be the default metadata for trace context propagation in case of Azure Service Bus.
[x] Create PR as draft
[ ] Approval by at least one other agent
[ ] Mark as Ready for Review (automatically requests reviews from all agents and PM via CODEOWNERS)
Remove PM from reviewers if impact on product is negligible
Remove agents from reviewers if the change is not relevant for them
[ ] Merge after 2 business days passed without objections \
To auto-merge the PR, add /schedule YYYY-MM-DD to the PR description.
So far, no agent had distributed tracing and span link support for Azure Service Bus. .NET implemented it recently and it uses the
diagnostic-id
application property - as suggested in the spec.For clarity and better compatibility across agents, this PR removes the word "possibly" - so
diagnostic-id
should be the default metadata for trace context propagation in case of Azure Service Bus.CODEOWNERS
)/
schedule YYYY-MM-DD
to the PR description.