Different monitoring times/escalations, same services

[Guy Knights]

Thank you, master. You are wise, like old yak.

I will follow your teachings on the path to enlightenment!

Thanks,
Grasshopper

P.S. It's been a slow week...

Greg Vickers wrote:

> Ah, grasshopper, you ask all the hard questions...
>
> Guy Knights wrote:
>
> <snip>
>
>> The servicegroup that this service is a member of follows a 
>> particular escalation pattern during our operating hours. However, on 
>> the weekend, we'd like the notification/escalation pattern to be 
>> completely different, as we don't want the person on call to be 
>> bombarded with text messages if they can't get to a PC to acknowledge 
>> the service problem.
>>
>> The number of services we want to monitor on the weekend is also much 
>> smaller than during the week. I can't, at the moment, see any other 
>> way to set up the notification schedule for on-call monitoring 
>> without creating multiple copies of services marked as "Check process 
>> [httpd] - weekday" and "Check process [httpd] - weekend" (for example).
>>
>> Does anyone have any suggestions as to how I can set this up? If I 
>> could just override notification timings in servicegroup 
>> descriptions, I think this would be the answer, but I'm almost 
>> certain that isn't possible.
>
>
> I think the answer you seek can be found here:
> http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#serviceescalation
>
> You would only have one service definition, but different copies of 
> the service escalation. The different copies of the service escalation 
> would have different escalation_period directives, i.e.:
>
> $ cat libsys-escalation01.cfg
> define serviceescalation{
>    hostgroup_name    redhat-servers
>    service_description    Check process [httpd]
>    contact_groups    libsys-DEC
>    first_notification    3
>    last_notification    6
>    notification_interval    5
> >>>   escalation_period    libsys-weekdays
>    escalation_options    w,u,c
> }
>
> $ cat libsys-escalation02.cfg
> define serviceescalation{
>    hostgroup_name    redhat-servers
>    service_description    Check process [httpd]
>    contact_groups    libsys-DEC
>    first_notification    2
>    last_notification    2
>    notification_interval    0
> >>>   escalation_period    libsys-weekend
>    escalation_options    w,u,c
> }
>
> So the above configuration would give you normal notifications until 
> the 3rd notification, during weekdays, (or whatever) then on weekends 
> give you only one additional notification after the first.
>
> So you would wind up with two copies of each service escalation - is 
> that less than doubling the number of services?
>
> And if you have multiple different escalations per service (I know you 
> do, don't hold out on us) then copy all escalations and apply the 
> appropriate time period. (Then you wind up with '2 x total number of 
> service escalations' - is that still less than your number of 
> services?? lol)
>
> Good luck!
>
> p.s. you must realise these truths before you can leave the temple, 
> grasshopper... yes, it's been a slow day
>


-- 
Guy Knights
Computer Systems Officer
Queensland University of Technology
Victoria Park Road
Kelvin Grove, QLD
Ph: (07) 3864 3350
Fax: (07) 3864 5890
Email: g.knights at qut.edu.au





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null