Notifying on a service when host is unreachable?

[Carroll, Jim P [Contractor]]

Ah.  It seems I misunderstood the original question.

When an intermediate link goes down and you have no way of knowing
what the status of the remote host (or services on that host) are,
what would you propose should happen?  Just because Nagios can't
reach the service in question, doesn't mean that the service isn't
providing useful functionality.

Having said that, is it possible that defining service dependencies
might help you achieve what you're looking for?

jc


> -----Original Message-----
> From: Jeff Smith [mailto:doc at neonova.net]
> Sent: Friday, May 30, 2003 2:34 PM
> To: Carroll, Jim P [Contractor]
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Notifying on a service when host is
> unreachable?
> 
> 
> The Service Contacts and the Host Contacts are the same contact group.
> 
> Thanks,
> Jeff
> 
> Carroll, Jim P [Contractor] wrote:
> 
> > What about adding the service contacts to the host contact list?
> > 
> > jc
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: Jeff Smith [mailto:doc at neonova.net]
> >>Sent: Friday, May 30, 2003 10:29 AM
> >>To: nagios-users at lists.sourceforge.net
> >>Subject: [Nagios-users] Notifying on a service when host is 
> >>unreachable?
> >>
> >>
> >>At my site we monitor a lot of network links.  Currently these are 
> >>defined as services on the host router they connect to.  This 
> >>causes a 
> >>problem when the link drops and the host becomes unreachable. 
> >> The way 
> >>it is currently setup all the contact information for the 
> >>circuit is in 
> >>the service definition such that when it pages the oncall 
> person will 
> >>have all the information neccessary to contact the proper provider. 
> >>However, since they are defined as services (which I believe 
> >>they should 
> >>be) when the host goes unreachable because the link went down 
> >>the only 
> >>notification sent is for the host.  Is there a way to force 
> >>the service 
> >>notification to be sent as well?  If not, the only other 
> >>solution, that 
> >>I can think of, is to define these as hosts instead of 
> services which 
> >>I'd rather not be forced to do.  Any other ideas?
> >>
> >>Thanks,
> >>Jeff
> >>-- 
> >>Jeffrey Smith
> >>Operations
> >>Neonova Network Services
> >>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>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
> >>_______________________________________________
> >>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
> >>
> > 
> > 
> > 
> > -------------------------------------------------------
> > 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
> > _______________________________________________
> > 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
> 
> -- 
> Jeffrey Smith
> Operations
> Neonova Network Services
> doc at neonova.net
> 919.460.3330
> 
> 


-------------------------------------------------------
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
_______________________________________________
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