Skip to content

Modifying down alerts runbooks #360

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

Merged
avlitman merged 1 commit into from
Mar 24, 2026
Merged

Modifying down alerts runbooks #360

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/runbooks/VirtAPIDown.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Meaning

This alert fires when all the API Server pods are down.
No running `virt-api` pod has been detected for 10 minutes.

## Impact

Expand Down
3 changes: 1 addition & 2 deletions docs/runbooks/VirtHandlerDown.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,7 @@

## Meaning

This alert fires when all `virt-handler` pods are down (no `virt-handler` pod
has been reported up for 10 minutes).
No running `virt-handler` pod has been detected for 10 minutes..

The `virt-handler` runs on every node that can schedule VMIs. It is
responsible for domain lifecycle, network configuration, and other
Expand Down
Loading