contacts question

[Andreas Ericsson]

Roy Kidder wrote:
> I'm trying to wrap my head around how to set up contacts/notifications for
> my instance of Nagios.
> 
> The entities I monitor, can be split into two categories: important (for
> lack of a better term), non-important. For example, the core switch in my
> network is important, whereas a router in a remote location (connected via
> DSL) is non-important.
> 
> I have two time periods I care about, 24x7, and business hours (bhours).
> 
> I have the standard two email addresses: email and pager.
> 
> I want to set up notifications thusly:
> 
> critical alert + important element + 24x7 = page and email
> critical alert + non-important element + bhours = page and email
> critical alert + non-important element + non-bhours = email
> warning alert + important element + 24x7 = email
> warning alert + non-important element + 24x7 = email
> 
> and obviously, I'd like to avoid duplicat alerts. I'd also like to have as
> few contact definitions per person as possible. Anyone have suggestions as
> to the best approach for this?
> 

There's no way of doing it without specifying dual contacts for every 
person. That's what you need to do when you want different notification 
options for the same people.

As for the rest, two different host and service-templates should do the 
trick.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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