I'm testing a passive check that has uptime of 30 minutes. It starts with status OK. When it's done, there are 23.5 hours of downtime.
An email is sent 5 minutes after the check is activated in an effort to reset the freshness counter to 0. Then, if some process is successful, it sends another email within the freshness period of 20 minutes (1,200 seconds).
I would expect that there would be no checking during downtime and that the status would remain OK. However, it seems that checks are done at random times during downtime and setting the status to 'Critical'.
Have I missed something in the settings to prevent this from checking during downtime?
Thanks.
Steve
Downtime and Freshness
Downtime and Freshness
You do not have the required permissions to view the files attached to this post.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Downtime and Freshness
Downtime doesn't stop the checks from being performed, it only stops the notifications from being sent.
Re: Downtime and Freshness
OK -- thank you, Scott.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Downtime and Freshness
Great!vornado wrote:OK -- thank you, Scott.
Locking