[Check_mk (english)] Check/Alert intervals

Fasal fasal.official3 at gmail.com
Tue Oct 15 08:44:53 CEST 2019

But it work in a different way in my latest raw version. The notification
only sent after 15 minutes (3*5) that is too long, ehich implies the 1
minute retry interval is not even taking.  When checking further I see thr
retry interval is only effective on Active checks, so the service check
shouldn't be under it that causing this situation. Any idea to overcome
this and sent alert only if the service/host in critical/down status for 3
or 4 minutes continuos.

Thanks Andreas!!

On Sat, Oct 12, 2019, 11:04 PM Andreas Döhler <andreas.doehler at gmail.com>

> Hi Fasal,
> not completely right. Normal check interval is in your setup 5 minutes.
> That means the longest time before the system can detect a problem is 5
> minutes.
> Then it tries 3 times with a 1 minute interval. After these three checks
> the state goes hard and a notification is sent.
> The result is a notification between 3 minutes and 8 minutes after the
> problem occurs.
> 3 minutes if the problems happens right before a normal check is executed
> and 8 minutes if the problem occurs directly after a normal check.
> To have a more predictable behavior I recommend the same interval for
> normal and retry checks if the problem should be notified.
> If the check is only for information like the "Check_MK discovery" then
> this is not so important.
> br
> Andreas
> Am Sa., 12. Okt. 2019 um 15:08 Uhr schrieb Fasal <
> fasal.official3 at gmail.com>:
>> Hey Guys,
>> Thanks for being so responsive on this lists, much appreciated.
>> This time, I need your advice on the check/alert intervals to make it
>> more good. I set the following rules:
>> Normal check interval for host/service checks: 5 minutes
>> Maximum number of check attempts for host/service: 3
>> Retry check interval for host/service checks: 1 minute
>> With the above, if one service/host went unresponsive or critical the
>> notification only generating after 15 minutes (3 time check * 5 minute
>> interval). The Retry Check Interval states, if the status did not change
>> the check will perform at this interval. If that is correct, the actual
>> notification would generate within 3 minutes instead of 15 minutes, right?
>> I may be understood incorrectly, can you correct me if I'm wrong? Also,
>> what would be the best setting/rule to avoid false-positive alerts and to
>> get the notification within 2-5 minutes when a host/service went down.
>> Thanks,
>> Fasal
>> _______________________________________________
>> checkmk-en mailing list
>> checkmk-en at lists.mathias-kettner.de
>> Manage your subscription or unsubscribe
>> https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mathias-kettner.de/pipermail/checkmk-en/attachments/20191015/75786c3b/attachment.html>

More information about the checkmk-en mailing list