More updates for the current OTel (OpenTelemetry) conventions #1717
+37
−25
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.
Proposed Changes
Update to latest OTel conventions
messaging.operation.name
tagBuilds on #1716.
Fixes #1715.
In order to get 7.0 released, this can wait until 7.1.
Types of Changes
What types of changes does your code introduce to this project?
Checklist
CONTRIBUTING.md
documentFurther Comments
Regarding #1715 (comment), I used
fetch
instead ofpolling fetch
orbasic.get
because:basic_
prefix.basic.get
.fetch
(in my mind) conveys a pull operation to me and is meaningfully distinguished fromdeliver
.