-
Notifications
You must be signed in to change notification settings - Fork 65
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
Stale marker accuracy #85
Conversation
b4feac3
to
e8c1012
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.
The new option LGTM, but I think some test issues should be addressed.
Changes addressed in #86. I created a new PR to have a consistent branch name. I will keep this for timestamp accuracy. |
395ee7f
to
2943fac
Compare
80f27c3
to
9fca3fd
Compare
9fca3fd
to
c3219f5
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.
Generally looks good 👍 (with the idea in my mind that I'm not familiar with the topic)
One thing that could be improved since we have time manipulation is to have more test cases, which could probably be done in the following PRs.
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.
I haven't tested this, but your explanation and test change makes sense. 👍
It introduces a new optionMoved to #86K6_PROMETHEUS_RW_STALE_MARKERS=<bool>
for enabling the Staleness marking process at the end of the test. It also disables the option by default.It adjusts the stale marker accuracy by adding slight padding.