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.

Sign up for GitHub

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

Jump to bottom

Create a metric+alert for detecting third party outages #2434

Open
majamassarini opened this issue May 30, 2024 · 0 comments
Open

Create a metric+alert for detecting third party outages #2434

majamassarini opened this issue May 30, 2024 · 0 comments
Labels
area/fedora Related to Fedora ecosystem 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

We did not detect soon the new hotness outage (and for some days there were no pull from upstreams in Packit)
In the past we did not detect problems on the Koji side.

The idea is to create a metric counting the number of received messages per day categorized by type, create a threshold for every type of message and send an alert if we are below the threshold.
@majamassarini majamassarini added the kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. label May 30, 2024
@lachmanfrantisek lachmanfrantisek added area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fedora Related to Fedora ecosystem 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
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@majamassarini @lachmanfrantisek