Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Messaging: protocol name requirement level and defaults #504

Closed
lmolkova opened this issue Nov 10, 2023 · 0 comments · Fixed by #644
Closed

Messaging: protocol name requirement level and defaults #504

lmolkova opened this issue Nov 10, 2023 · 0 comments · Fixed by #644
Assignees
@pyohannes

Comments

@lmolkova
Copy link
Contributor

lmolkova commented Nov 10, 2023 •
edited
Loading

Messaging systems frequently support just one protocol (e.g. RabbitMQ works on top of AMQP 0.9.1 and Azure SerivceBus works on top of AMQP 1.0)

Setting protocol name should not be necessary as long as messaging.system is set and protocol version is implied.

this would be consistent with HTTP where protocol name is only required when it's not http.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pyohannes pyohannes

Labels
None yet
Projects
Spec: Messaging Semantics
Status: Post-stability
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make network.protocol.name conditionally required for messaging pyohannes/semantic-conventions
3 participants
@lmolkova @arminru @pyohannes