Conversation
…e after the budget is already exhausted
kovayur
requested review from
ebensh and
johannes94
and removed request for
a team and
ebensh
kovayur
changed the title
johannes94
approved these changes
Mar 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem: Error budget exhaustion alert is fired for a small downtime after the budget is already exhausted
Changes:
min_over_time(central:sli:availability[1h])withcentral:slo:availability:burnrate1h >= 15for the error budget exhaustion alerts to accept small downtimes due to pod restarts (cluster or operator upgrades).min_over_time(central:sli:availability[1h])for the error burn rate alert because this condition is basically equivalent tocentral:slo:availability:burnrate1h > 0which will be always true if the other condition is true (burnrate1h > 30)