Specify LastValue for ValueObserver, TBD for ValueRecorder #984
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
arminru
reviewed
Sep 22, 2020
carlosalberto
approved these changes
Sep 22, 2020
bogdandrutu
approved these changes
Sep 22, 2020
arminru
approved these changes
Sep 22, 2020
jkwatson
approved these changes
Sep 22, 2020
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
…metry#984) * Specify LastValue for ValueObserver, TBD for ValueRecorder * Changelog * Changelog2 * Fix Changelog
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 #834.
Changes
Apply the decision in #834. The ValueObserver instrument should use LastValue aggregation by default, since those are the semantics of the instrument itself. Clarify that #625 has not been decided. See also #982.