Notification level Was: COMPLETE: RFE(x2): Service Info/Notify Method On Level

[Subhendu Ghosh]

On Thu, 5 Jun 2003, Brandon Knitter wrote:

> > > NOTIFY METHOD:
> > > This allows a service to say that it should only be notified via EMAIL or
> > PAGER
> > > or BOTH based upon the new state (ok, warn, crit, unknown).  If nothing is
> > > specified for the service then the default BOTH is choosen (or p,e) which
> > is
> > > basically what we all know of today.
> > > 
> > > This is kind of cheap as it simply checks the notification command for the
> > > $CONTACTPAGER$ or $CONTACTEMAIL$ entry in the raw_command string.  If it
> > exists,
> > > then it's considered that type of notification command (or both) and acts
> > > accordingly on it.
> > 
> > Rather than having Nagios do this centrally, it would be better to 
> > create a notification script that took the various macros as 
> > arguments and decided how to notify the contact.  This is especially 
> > true now that there will be six additional address fields for 
> > contacts in 2.0.
> 
> What we really need is a way to be able to say "email on warning" and "page on
> critical".  We don't want to do this for every service, just some of them.  So
> if I wanted to do this via a script I would need two different contacts for each
> person, as well as two different contactgroups for each set of people, then I
> could choose the contact group based upon the service's notification type I
> want.  Obviously a workaround, but a hack.
> 
> Are there any plans to put the notification level closer to the server rather
> than just on the contact?  Combining this with notification type (page, email)
> on the service would make it so that I can clearly fine tune the notification
> types for an individual service.  Of course, if it's not defined on a service
> (making it an optional field) then it could just fall back to the contact's
> preference (service's configuration take's precedense).
> 
> Just throwing out ideas!
> 

The best way of course would be to pass some $ARG#$ to the notification 
script from the service definition
(e.g. pointer to 4th contact definition)

-- 

-sg



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.