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

[Brandon Knitter]

I've completed development on my requested two features against the 1.0 releast
codebase.  To recap:

SERVICE INFO:
This is a new server config entry called "full_description" which can store
freeform text, including html.  It just plops it in right above the service
comments.

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.

NAGAT:
I'm not sure who's maintaining Nagat, but I encorporated these changes into the
1.0a2 release (that's what I had handy) including multiple bug fixes, sorting
inhancements, etc.


So, what's the best way to present these?  I was going to make patches for them
and just post them at my site if people are interested?

I'm still testing and such, but the meat of the work is done.

Thanks,

-- 
-bk


Quoting "Carroll, Jim P [Contractor]" <jcarro10 at sprintspectrum.com>:

> Brandon Knitter wrote:
> > > Service Info
> > This would be an addition config entry for Hosts and Services 
> > which would allow
> > for free form text to be included in a pop-up at the 
> > Service/Host screens.  This
> > would include things such as service/host background, how to 
> > test it, and how to
> > fix it.  It would be great to consolidate this in a single 
> > place.  If this is
> > not available, then at least a Service Info Link would be 
> > really cool. 
> > Something that helps the tech find the appropriate 
> > information about the problem.
> 
> We could use this feature as well.  Would be great for adding free-form info,
> such as serial numbers, primary application(s), trouble ticket numbers,
> escalation points of contact, just to name a few.
> 
> > > Notify Method On Level
> > There are a lot of cases (disk space for instance) where we 
> > would prefer to be
> > emailed on WARNING and paged on CRITICAL.  Currently this is 
> > not possible as you
> > have to choose the contact and contactgroup for the service, 
> > irrespective of the
> > state level.
> 
> Many have wondered how to do this in the past.  The solution (workaround?)
> has been to create one contact for e-mail and another contact for pager.  In
> our particular environment, all the admins have their own e-mail addresses,
> and we have a virtual pager which is a separate entry in contacts.cfg.  Works
> well, even if it's not intuitive for the Nagios neophyte.
> 
> jc
> 
> > 
> > Any thoughts?
> > 
> > 
> > -- 
> > -bk
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
> 
> 




-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5