Add alternate expression for ipmi down alert#828
Open
daaang wants to merge 1 commit intoproductionfrom
Open
Conversation
This shares the same alert name, summary, labels, and for value with the
existing `up{job="ipmi"} == 0` alert. Sometimes when a lights out device
is not responding, the ipmi exporter does respond like this:
# HELP ipmi_up '1' if a scrape of the IPMI device was successful, '0' otherwise.
# TYPE ipmi_up gauge
ipmi_up{collector="bmc"} 0
ipmi_up{collector="chassis"} 0
ipmi_up{collector="ipmi"} 0
If this happens, the corresponding `up` value will be `1` since there
was a response with any metrics, even if that response happens to be
"everything I tried to talk to is down."
So this adds a `ipmi_up{collector="ipmi"} == 0` condition. It's fine for
these to share a name in part because they will never fire at the same
time:
1. If `up == 0` then there are no metrics, so `ipmi_up` cannot also `== 0`.
2. If `up == 1` then an alert only fires if `ipmi_up` is `== 0`.
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
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.
This shares the same alert name, summary, labels, and for value with the existing
up{job="ipmi"} == 0alert. Sometimes when a lights out device is not responding, the ipmi exporter does respond like this:If this happens, the corresponding
upvalue will be1since there was a response with any metrics, even if that response happens to be "everything I tried to talk to is down."So this adds a
ipmi_up{collector="ipmi"} == 0condition. It's fine for these to share a name in part because they will never fire at the same time:up == 0then there are no metrics, soipmi_upcannot also== 0.up == 1then an alert only fires ifipmi_upis== 0.