Metrics SDK - require meter information to be available for exporter#2040
Merged
jsuereth merged 5 commits intoopen-telemetry:mainfrom Oct 25, 2021
Merged
Conversation
reyang
added
area:sdk
arminru
approved these changes
Oct 20, 2021
jmacd
approved these changes
Oct 21, 2021
jsuereth
approved these changes
Oct 21, 2021
cijothomas
approved these changes
Oct 21, 2021
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this pull request
Oct 31, 2024
…pen-telemetry#2040) * Metrics SDK - require meter information to be available for exporter * update changelog
schmikei
pushed a commit
to schmikei/opentelemetry-specification
that referenced
this pull request
Apr 17, 2025
Co-authored-by: otelbot <197425009+otelbot@users.noreply.github.com> Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Partially address issue #1906 (there is the semantic convention part which is NOT being addressed here).
An alternative approach was proposed here #2035.