Re: [Nagios-users] Nested notifications; parent vis-a-vis parent_host

2007-07-04 Thread Marc Powell


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nagios-users-
 [EMAIL PROTECTED] On Behalf Of Lev Lafayette
 Sent: Tuesday, July 03, 2007 9:50 PM
 To: nagios-users@lists.sourceforge.net
 Subject: Re: [Nagios-users] Nested notifications;parent vis-a-vis
 parent_host
 
 On Tue, 2007-07-03 at 22:23 -0400, Morris, Patrick wrote:


  If you don't want the UNREACHABLE alerts, just disable them.
 
 Yeah, I've done that. Just does seem to be pretty redundant to send
out
 UNREACHABLE alerts when a parent is DOWN, imo... :-)

It has it's benefits. That's why it can be enabled and disabled, just
like all the other notification types.

--
Marc


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Nested notifications; parent vis-a-vis parent_host

2007-07-03 Thread Morris, Patrick
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:nagios-users-
 [EMAIL PROTECTED] On Behalf Of Lev Lafayette
 Sent: Tuesday, July 03, 2007 6:29 PM
 To: nagios-users@lists.sourceforge.net
 Subject: Re: [Nagios-users] Nested notifications;parent vis-a-vis
 parent_host
 
   However, when the parent machine goes down, all the VMs (for
 obvious
   reasons) send out a Oh Noes! message as well. This is not
wanted.
  
 
  Shouldn't happen if your host checks work properly and you have the
  parents directive properly set up to match your environment.
 
 
 To be more specific, when a border-router or similar goes down,
 unreachable notifications are sent out for a number of connected
 machines, vms and so forth; which is pretty obvious imo... This seems
 to
 be the main issue DOWNs leading to UNREACHABLES.

If you don't want the UNREACHABLE alerts, just disable them.

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Nagios-users mailing list
Nagios-users@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


[Nagios-users] Nested notifications; parent vis-a-vis parent_host

2007-07-02 Thread Lev Lafayette

Hey nagios people,

Assume I have a happy system of a hypervisor and virtual machines.
Further, there's a neat system of when a machine goes down an SMS and
email is sent to the responsible person.

However, when the parent machine goes down, all the VMs (for obvious
reasons) send out a Oh Noes! message as well. This is not wanted.

Now the nagios documentation, dating back from the netsaint days, says
the system to walk a dependency path using parent_host... however the
hosts.cfg has entries like the following:


define host{
use generic-host; Name of host
template to use
host_name   guestvm1
alias   guestvm1
address xxx.xxx.xxx.xxx
parents xendom0
check_command   check-host-alive
}

Now presumably, cgis like statusmap.cgi is built from this information.
Would changing 'parents' to 'parent_map' in the above fix the dependency
walk and notifications? And would it break statusmap.cgi?

Thanks in advance,



Lev


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Nagios-users mailing list
Nagios-users@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