feat(azure_servicebus): add azure servicebus integration and function trigger distributed tracing #13691
+2,601
−217
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ced directly from the context
… related to service bus
…ctions and azure_servicebus
![datadog-datadog-prod-us1[bot]](https://avatars.githubusercontent.com/u/365230?s=60&v=4){kind=small}
|
|
duncanpharvey
changed the title
Bootstrap import analysisComparison of import times between this PR and base. SummaryThe average import time from this PR is: 277 ± 3 ms. The average import time from base is: 277 ± 2 ms. The import time difference between this PR and base is: 0.0 ± 0.1 ms. The difference is not statistically significant (z = 0.41). Import time breakdownThe following import paths have appeared:
|
BenchmarksBenchmark execution time: 2025-06-23 22:25:31 Comparing candidate commit 7a55f4d in PR branch Found 0 performance improvements and 3 performance regressions! Performance is the same for 558 metrics, 3 unstable metrics. scenario:iastaspects-upper_aspect
scenario:iastaspectsospath-ospathbasename_aspect
scenario:iastaspectsospath-ospathjoin_aspect
|
emmettbutler
approved these changes
Jun 17, 2025
…'t reuse service bus messages
ZStriker19
approved these changes
Jun 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds an integration for tracing the producer of the azure-servicebus package and adds support for distributed tracing for Azure Functions consuming the service bus messages.
Instrumentation details:
azure.servicebusandazure.servicebus.aio(async package) are patchedServiceBusSender.send_messagesServiceBusSender.schedule_messagesapplication_propertiesof each service bus message passed to above methodsServiceBusMessageorAmqpAnnotatedMessagein addition to a list ofServiceBusMessageorAmqpAnnotatedMessageServiceBusMessageBatchin a future PRapplication_propertiesin Azure Function service bus consumercomponent: azure_servicebusspan.kind: producerspan.type: workeroperation: azure.servicebus.producemessaging.destination_kind- not set, instances ofServiceBusSenderdon't specify whether it is a queue or topic they are sending tomessaging.destination.name: <queue/topic name>messaging.destination.system: servicebusmessaging.operation: sendnetwork.destination.name: <fully qualified host name for Service Bus namespace>network.destination.port- not set, no port specified on instances ofServiceBusSenderAdditional Notes:
azureservicebusemulatorandazuresqledgeservices to run Azure Service Bus locally and in CI for testsazure_functionsintegration to usectx.spaninstead of addingreq_spanandtrigger_spanproperties to the contextChecklist
Reviewer Checklist