Changing Notification Periods

[Subhendu Ghosh]

Not really - you are trying to create a down time for the host.  The 
use of timeperiods would be recommended if it was the same time all the 
time.

I think you are try to shoe horn a process issue - the backup folks forget 
to schedule the downtime - into a timeperiod config issue.

The way to get the backup folks involved in this is to set them up as a
contact for Sunday 0200 - 0600 - This way if they forget to schedule the
down time they too will get paged and have an "oh s**t" before you call
in.  If they schedule the downtime - nobody gets paged and evrybody stays 
happy (relatively :)

Besides, everytime you change the cfg, the nagios process has to restart 
and you loose a small monitoring window.

If you really want to use timeperiods, why not increase the exempt 
timeperiod from 0300 to 0600 to cover 3-5 or 4-6 since the ablility to 
change the backup window implies there is some flexibility in that 
timeperiod for availablility.

If you do use the downtime feature - note that you can use the flexible  
downtime such that the a downtime can start anywhere in the window 
specified, but then will last for a period equal to the window.

So a flexible downtime of 0300-0500 will cover both 0300-0500 and 
0400-0600 or 0459-0659 if you require 2 hours for the backup.

-sg

On Fri, 6 Sep 2002, Rusch, Daniel wrote:

> Thanks for the reply.  
> 
> I thought of both of your suggestions.  Let me try to explain a little
> better.  It's more than just scheduling "down time"  we are really talking
> about changing the timeperiods.  We don't want people to be required to
> "schedule down time" (they will forget and I get paged). Normally, the
> systems are backed up/maintained at the same time each week/day but on
> occasion they need to change when the backup/maintenance occurs.  
> 
> For example:
> 
> # 'LEXM' timeperiod definition
> define timeperiod{
> 	timeperiod_name	LEXM
> 	alias		LEXM
> 	sunday		00:00-04:00, 06:00-24:00
> 	monday		00:00-24:00
> 	tuesday		00:00-24:00
> 	wednesday	00:00-24:00
> 	thursday	00:00-24:00
> 	friday		00:00-24:00
> 	saturday	00:00-24:00
> 	}
> 
> 
> 
> look at Sunday's entry.  From 4 to 6 am,  outages will not be reported.
> Let's say that they need to change that to 3 to 5.  Is there an easy way to
> do it without editing the cfg file.
> 
> Dan
> 
> 
> 
> -----Original Message-----
> From: Subhendu Ghosh [mailto:sghosh at sghosh.org]
> Sent: Thursday, September 05, 2002 10:17 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Changing Notification Periods
> 
> 
> On Thu, 5 Sep 2002, Rusch, Daniel wrote:
> 
> > All,
> > 
> > How do you handle hosts that the weekly scheduled downtime keeps changing.
> > For example, I have a system call it Homer that normal goes down for
> > database backup etc. On Sunday morning at 3 am to 4 am.  But about twice a
> > month or so they want to change the time to something else (say 4 am to 5
> > am).  How do you handle this.  I currently as a admin go in and hand edit
> > the cfg file. It's no big deal for one server but do it for 50, agh...  Is
> > the a way to allow a "special trusted user" to change this time through
> the
> > nagios interface?
> > 
> > Thanks,
> > 
> > Dan
> > 
> 
> why edit the cfg?
> 
> Anyone who is a contact for the host/service should be able to schedule a 
> downtime.  Alternatively a script to submit an external command the 
> submits the following:
> 
> SCHEDULE_SVC_DOWNTIME;host;service_name;start epoch;end epoch;fixed=1
> otherwise=0;duration (sec);contact name;comment
> 
> SCHEDULE_HOST_DOWNTIME;host;service_name;start epoch;end epoch;fixed=1
> otherwise=0;duration (sec);contact name;comment
> 
> 
> 

-- 





-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390