Nothing. I only wanted to be clear that this is the desired state and I don’t want to translate it through a rule to always UP.
mgutt:or something like “Ignore problems of hosts …”?
Can you explain in detail what you expect? What do you want to “ignore”
CheckMK should not treat a DOWN host as a problem. Not sure how to explain it different ^^
Or maybe the workflow as an example:
Step 1: Check if there are any unhandled problems
Step 2: Check problems, solve them or acknowledge them with a comment
Its the standard Nagios behavior. First its an soft alert and after reaching max check attempts it change to a hard state. A hard state trigger a notification.
Yes, but the soft state already triggers an unhandled problem, which I think is incorrect.
Yes, you can do this with an alert handler and livestatus.
Hmm… So I need to create a BASH script which sends a request to the CheckMK API? Wouldn’t be my favorite solution as not doable by all team members.