-
Notifications
You must be signed in to change notification settings - Fork 889
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
Add semantic convention attributes for capturing the application layer protocol #2602
Add semantic convention attributes for capturing the application layer protocol #2602
Conversation
For the namespace name, ideally it should also fit with option 1 or 2 in #2607. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed it in messaging SIG and it makes sense to me, as well as introduces clarity to messaging instrumentation scenarios (current messaging.protocol
and messaging.protocol_version
does not feel right).
I support this change
cccc578
to
b28c337
Compare
Fixes #2548
Changes
This PR proposed the two additional attributes
net.app.protocol.name
andnet.app.protocol.version
. These allow capturing the name and version of the application layer protocol used (in addition to the name of the transport protocol captured in net.transport). The naming is consistent with ECS, where network.protocol is used.Those general attributes can be used to capture information about application layer protocols for which no dedicated semantic conventions exist (e. g. AMQT, or MQTT).
@Oberon00 proposed using a new
net.app
namespace for this.