-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service Bus Async with Opentelemetry: receiver._add_span_request_attributes never awaited #29199
Comments
Hi there @erewok . Thank you for the feedback, I think we had a similar issue where we addressed it but looks like another one snuck in. |
Looks like it will be taken care of by this PR #28761 |
Sounds good @kashifkhan. We can close this one and I'll look for that release. Thanks for the update. |
Ill close it once it goes out :) |
Appreciate it. Apologies: I should have searched before opening this. I just had this feeling that the async-servicebus+otel users would be a smallish group at this point... 🤷 |
@erewok no worries about that at all :) |
Hi @erewok , we released a new version of azure-servicebus yesterday with the fix for this. Thank you :) |
Sounds good. Thanks for letting me know. |
Package Name:
azure-servicebus = "^7.8.2"
azure-core-tracing-opentelemetry = "^1.0.0b9"
Operating System: OSX/Debian Container
python:3.11-slim-bullseye
Python Version: 3.11.2
Describe the bug
Async service-bus receiver with opentelemetry enabled warns:
To Reproduce
Steps to reproduce the behavior:
I made a gist which reproduces this: https://gist.github.com/erewok/7cf27c54673f0e6fa0265e5ef24df6ff
Expected behavior
No warnings: span-context is added as expected.
Additional context
It looks like this method is async but it's being called by this sync method.
Worth noting: the python opentelemetry implementation may be changed in the future to support async spans.
Also: sending a message does not show the same warning in the logs.
The text was updated successfully, but these errors were encountered: