This repository was archived by the owner on Apr 28, 2025. It is now read-only.
Fine tune CortexIngesterReachingSeriesLimit alert #404
Conversation
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
Signed-off-by: Marco Pracucci <[email protected]>
pstibrany
approved these changes
Oct 13, 2021
simonswine
pushed a commit
to grafana/mimir
that referenced
this pull request
Oct 18, 2021
…rtexIngesterReachingSeriesLimit Fine tune CortexIngesterReachingSeriesLimit alert
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
What this PR does:
I propose to increased
CortexIngesterReachingSeriesLimitwarning threshold from 70% to 80% and critical threshold from 85% to 90%.Reason is to try to reduce a bit the noise from this alert. With an organic grow of series, it takes time to do a 10% jump, so even a 10% room once the critical alert is fired should be enough to address it. On the other side, if we get a sudden jump (eg. because of a misconfiguration) we'll not have time to address it before the limit is hit anyway (so we'll hit the limit, get paged and then we'll address it).
Which issue(s) this PR fixes:
N/A
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]