Thank you Andreas and Marcel, that helped :)
Post by Andreas DöhlerHi Predrag,
the max check attempts rule activates SOFT states, which are not notified. With the nth attempt the state type changes to HARD and gets notified.
OK states are always HARD.
* hostA, hostB and hostC are checked every minute
* max check attempts for hosts is set to 3
* notification delay is set to 3 minutes
* hosts are all considered DOWN (SOFT) at 12:00
* hostB is UP (HARD) again at 12:01
* hostA and hosts are still DOWN at 3rd try 12:02 and change to HARD
* hostA is UP again at 12:20
* hostC is up at 12:04
* no other changes
...hostA gets notified about its DOWN state at 12:05 (12:02 +3 mins delay) and about its UP state at 12:23 (12:20 +3 mins delay). HostC does not get notified about its DOWN state (comes UP during delay time) but about its UP state at 12:07 (12:04 +3 mins delay). State changes of hostB are not notified at all (all during SOFT states).
Hope this helps in understanding the rules a bit more.
Regards,
Marcel
The restriction settings are only available inside "rule based notifications". Inside the old flexible notification system you had also such a setting. I cannot remember at the moment how the name was.
If you don`t want to get the "Up" message it is better to only make a setting for "Delay .... notifications" as it is written inside the description of the setting it will only sent notifications if the host is not ok again inside the time span.
Best regards
Andreas
Hi Andreas,
Thank you for your answer. I've set "Maximum number of check attempts for host" to 3, and "Delay host notifications" to 3 minutes. I don't know where to find "Restrict to n-th to m-th notification".
Anyway, there are now no notifications when a host goes down (unless it's down for 3 minutes), but I would still get "Host state: UP" even if "Host state: DOWN" was never sent... do you have any other tip?
Thanks,
Predrag
Post by Andreas DöhlerHi Predrag,
you can use for this the settings "Maximum number of check attempts for host", "Delay host notifications" and if you are using the rule based notification system "Restrict to nth to mth notification".
The first two settings will directly influence the time a notification is triggered by the monitoring core. The last setting will only generate an notification after some time if the problem persists. The first two settings are also available for services, if your check is not a host check.
Best regards
Andreas
Hi,
I have a host which connects to the Internet via a 3G modem, and because of that, notifications for host down/up are coming in more often than I'd like to.
I'd like to configure Check_MK to check this host x number of times before it sends notification that it is down, but also to check it x number of times before it sends notification that it is back up.
If there is something similar to SmokePing patterns - http://oss.oetiker.ch/smokeping/doc/smokeping_config.en.html <http://oss.oetiker.ch/smokeping/doc/smokeping_config.en.html> - that'd be great. Or any other solution really :)
Thanks!
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en <http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en>
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en <http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en>
_______________________________________________
checkmk-en mailing list
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en