-
Notifications
You must be signed in to change notification settings - Fork 638
Upgrade mimir-prometheus #10826
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
Upgrade mimir-prometheus #10826
Conversation
0457ed9
to
ef0e1c2
Compare
… range Brings in change from #10586
…te` and `increase` if the second point is a reset (prometheus/prometheus#15902)
71c0ab9
to
6f913d7
Compare
50c217f
to
001ae48
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.
lgtm, thanks for working on this! Just one new change that I don't think is adequately tested.
}, | ||
}, | ||
} | ||
|
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.
What about a test case for when the second last point and last point change types, and don't change types (in both orders)?
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.
This is quite difficult to test completely due to prometheus/prometheus#14172.
The test cases added upstream and included in this PR should cover most of the scenarios: float then float, float then histogram and histogram then histogram. Histogram then float is blocked by prometheus/prometheus#14172.
Are there other scenarios you had in mind?
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 missed those, thanks. lgtm
What this PR does
This PR upgrades mimir-prometheus to include the changes from grafana/mimir-prometheus#837.
I've added a changelog entry for one of the fixes in that set of changes, however the remainder don't seem worthy of a changelog entry (eg. because they're not relevant for Mimir, or are for experimental native histograms).
I've tried to build up this PR incrementally. I would suggest reviewing each commit separately.
Which issue(s) this PR fixes or relates to
(none)
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.