-
Notifications
You must be signed in to change notification settings - Fork 933
Recommend using a time-weighted reservoir sampling algorithm for histograms #4678
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
base: main
Are you sure you want to change the base?
Conversation
de93eba
to
80f9b71
Compare
80f9b71
to
106246d
Compare
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.
Looks good overall.
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
There is a concern from @tigrannajaryan that this is a breaking change. @jsuereth says there is language that allows us to make this change in the spec |
Feedback from @austinlparker: We should be careful about how we communicate this to users. Is there a way to make this opt-in for users? |
@carlosalberto requests that we leave this open for comment for a while. |
|
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.
Nice. This was a goal of mine in the original version, glad to see it improve.
I believe this is Jeffrey Vitter's "Algorithm R", for the record.
I might call this "time-unbiased" or "temporal uniform", not time weighted. |
Fixes #4675
Changes
Change the recommended algorithm for histogram reservoirs to be time-weighted.
I've left the previous algorithm as an option to ensure this change is backwards-compatible.
Go prototype: open-telemetry/opentelemetry-go#7458
CHANGELOG.md
file updated for non-trivial changes