Skip to content
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

Fix SLO1 rule definition #2520

Open
majamassarini opened this issue Sep 6, 2024 · 0 comments
Open

Fix SLO1 rule definition #2520

majamassarini opened this issue Sep 6, 2024 · 0 comments
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@majamassarini
Copy link
Member

majamassarini commented Sep 6, 2024

After point 1. in #2519 is solved we can fix SLO1 rule definition.
If in the graph there are more than 1 event/min of no_status_after_25_s than an alert should be fired.
Now it isn't - unless we have a burst of events - the considered time range is too broad and we have too few events.

@majamassarini majamassarini added complexity/easy-fix area/other Related to some other area/category than the specified ones. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Sep 9, 2024
@majamassarini majamassarini moved this from new to backlog in Packit Kanban Board Sep 9, 2024
@lachmanfrantisek lachmanfrantisek added complexity/single-task Regular task, should be done within days. and removed complexity/easy-fix labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Status: backlog
Development

No branches or pull requests

2 participants