<html>
<head>
</head>
<body>
The way nagios handles downtime (assuming you are talking about entering
in scheduled downtime) is as a suppression of notifications, not a suppression
of checks. If you put a host into a scheduled downtime, the service check
will occur still. If that service is down, nagios will then do a host check.
If the host is down (the downtime has begun), it will show that the host
is down. But when it goes to do the notification, it checks to see if the
host is in a period of downtime. Since it is, the notifications will not
go out, but the host will be in a down state, not assumed OK.<br>
<br>
This is actually beneficial if the downtime ends and for some reason a problem
still exists. The host or service should have come back up but hasn't. So
instead of having to go through all the retries (if you have retries set
up), the host/service is already in a Hard non-OK state, so you will get
notified after the first check.<br>
<br>
-Russell<br>
<br>
Nicole Hähnel wrote:<br>
<blockquote type="cite" cite="mid:001001c263d0$f3524e00$13121bac@pc1072">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">Hi,</font></div>
<div><font face="Arial" size="2">what is the best way to specifiy down
times for server/services?</font></div>
<div><font face="Arial" size="2">Nagios should not check the service and
assume up for this time.</font></div>
<div><font face="Arial" size="2">It should not affect uptime statistics.</font></div>
<div> </div>
<div><font face="Arial" size="2">Gruss</font></div>
<div><font face="Arial" size="2">Nicole</font></div>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
Russell Scibetti
Quadrix Solutions, Inc.
<a class="moz-txt-link-freetext" href="http://www.quadrix.com">http://www.quadrix.com</a>
(732) 235-2335, ext. 7038
</pre>
<br>
</body>
</html>