-
Notifications
You must be signed in to change notification settings - Fork 903
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
Rename None aggregation to Drop #2101
Rename None aggregation to Drop #2101
Conversation
From one point of view I agree with this, WDYT of this change in relation to: #2102 |
We've discussed this during the 11/11/2021 Metrics SIG Meeting, folks think I suggest that we move forward and merge the PR before Stable release. |
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.
+1 for Drop: dropping values has different meaning than not aggregating them.
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.
Approve pending Armin's comment
* Rename None aggregation to Drop * fix compliance * fix compliance * changelog Co-authored-by: Joshua MacDonald <[email protected]>
Drop feels like a better name than "none". Want to check if others feel the same.
"The None Aggregation informs the SDK to ignore/drop all Instrument Measurements for this Aggregation."
Found some history: https://github.com/open-telemetry/opentelemetry-specification/pull/956/files