We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
messaging.system
this would be consistent with HTTP where protocol name is only required when it's not http.
http
The text was updated successfully, but these errors were encountered:
network.protocol.name
pyohannes
Successfully merging a pull request may close this issue.
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
.The text was updated successfully, but these errors were encountered: