Increased CortexIngesterReachingSeriesLimit critical alert threshold from 80% to 85% #363
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:
The
CortexIngesterReachingSeriesLimit
alert currently has two threshold:The warning alert is currently discussed in #362 while this PR is focusing on the critical alert.
What we've learned from production about ingesters reaching series limit:
Because of this, I would propose to fire the critical alert once we reach the 85% utilization (instead of the current 80% threshold). This will still leave us a 15% room before hitting the limit, which typically gives us enough time to address without any customer-facing disruption.
This change, together with the change we're doing in #362, should help to improve
CortexIngesterReachingSeriesLimit
alert to fire only when there's actually an action to take.Which issue(s) this PR fixes:
N/A
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]