Make network.protocol.name conditionally required for messaging
#644
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pyohannes
changed the title
network.protocol.name conditionally required for messaging
joaopgrassi
reviewed
Jan 18, 2024
joaopgrassi
approved these changes
Jan 19, 2024
arminru
approved these changes
Jan 22, 2024
jsuereth
approved these changes
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #504
Changes
This makes the usage of
network.protocol.nameconsistent between messaging and HTTP semantic conventions: it is now conditionally required for both metrics and traces if the protocol name isn't obvious for the given messaging system or framework.This is a breaking change for messaging instrumentations, as a previously recommended attribute is made conditionally required.
Merge requirement checklist
schema-next.yaml updated with changes to existing conventions.