-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[FEATURE REQ] Service Bus/EventHubs tracing conform to the semantic conventions of messaging systems #21686
Labels
Milestone
Comments
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
May 20, 2021
srnagar
added
Client
This issue points to a problem in the data-plane of the library.
Service Bus
and removed
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
labels
May 20, 2021
36 tasks
14 tasks
anuchandy
changed the title
Service Bus tracing - conform to the semantic conventions of messaging systems
[FEATURE REQ] Service Bus - tracing conform to the semantic conventions of messaging systems
Apr 26, 2022
merging it with #21684 - messaging semantic conventions live in azure-core-tracing-opentelemetery and not library-specific |
lmolkova
changed the title
[FEATURE REQ] Service Bus - tracing conform to the semantic conventions of messaging systems
[FEATURE REQ] Service Bus/EventHubs tracing conform to the semantic conventions of messaging systems
Aug 24, 2022
This was referenced Feb 18, 2023
This can now be closed - Azure messaging libs follow otel messaging semconv |
github-project-automation
bot
moved this from In Progress
to Done
in Java SDKs Azure Core
Feb 10, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Service Bus SDK should conform and fit the above path used for other messaging systems but no rush as messaging semantic conventions may still change.
See this reference PR
The text was updated successfully, but these errors were encountered: