Skip to content

Fix VMNonRecoverableOSPanic to reflect both >0 and >5 cases #390

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

Open
avlitman wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix VMNonRecoverableOSPanic to reflect both >0 and >5 cases #390

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
4 changes: 2 additions & 2 deletions docs/runbooks/VMNonRecoverableOSPanic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@

## Meaning

This alert fires when a VM has experienced more than 5 non-recoverable guest
OS panics in the last 24 hours. The alert is based on the
This alert fires when a VM has experienced non-recoverable guest OS panics in
the last 24 hours. The alert is based on the
`kubevirt_vmi_guest_os_panic_total` metric, which tracks panic events for all
panic types (pvpanic, hyper-v, s390, etc.).

Expand Down