Add an alert for when querier index cache churn rate is too high. #26
Conversation
This file contains 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: Callum Styan <callumstyan@gmail.com>
cstyan
force-pushed
the
cache-churn-alert
branch
from
a66b866
to
1520666
Compare
|
bump @gouthamve |
gouthamve
requested changes
Apr 22, 2020
| @@ -226,6 +226,22 @@ local windows = [ | |||
| |||, | |||
| }, | |||
| }, | |||
| { | |||
| alert: 'CortexQuerierIndexCacheChurnRate', | |||
There was a problem hiding this comment.
The metrics here are for the in-mem fifo-cache imo. We kinda don't care about the fifocache churn rate, but rather about the memcache churn rates.
The query should be sum without (job) (memcached_current_items) / sum without (job) (rate(memcached_items_evicted_total[5m])) < 3600.
It shouldn't be for just index cache, but rather all caches.
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's been a while since I did anything interesting with queries/label substitution and alerts, so let me know what we could change here to make sure this alert is useful. I based the
entries in cache < 10mbit based on our env with the lowest value forentries in cache / churn rate / 60sbeing an average ofentry in cache for 12+ minutes, but for other environments we have anything from 30-60 minutes.Signed-off-by: Callum Styan callumstyan@gmail.com