Re: [Nagios-users] Nagios implied and additive inheritance

2012-03-28 Thread Jim Winkle
Thanks for the workarounds.

I'm still not sure if this is a bug or if this is the way it's intended to work,
so I will repost on the nagios-dev list.

-- Jim

On Mon, 26 Mar 2012 13:04:00 -0500 Jim Winkle jwin...@doit.wisc.edu wrote

 I'd like to set up Nagios so that:
 1) In general, contact_groups for a host are notified about problems with the
 host and any service on the host.
 2) Occasionally, we'd like other contact_groups to be notified about problems
 with certain services on the host.
 
 If I'm understanding the documentation at
 http://nagios.sourceforge.net/docs/nagioscore/3/en/objectinheritance.html
 correctly, it indicates that #1 can be done using implied inheritance and #2
 by using additive inheritance, but it's not working as expected.  I've found
 other posts from people with the same issue, but never any resolution.
 
 For example, if I define:
 
 define host{
     host_name   linux-server
     contact_groups  linux-admins
     ...
     }
 
 define service{
     host_name   linux-server
     service_description l_proc_sshd
     contact_groups  +management
     ...
     }
 
 
 I would like this to be equivalent to:
 
 define service{
     host_name   linux-server
     service_description l_proc_sshd
     contact_groups  linux-admins,management
     ...
     }
 
 But instead, the implied inheritance of linux-admins is ignored, and it's
 equivalent to:
 
 define service{
     host_name   linux-server
     service_description l_proc_sshd
     contact_groups  management
     ...
     }
 
 So contact_groups is overwritten rather than added to.  No warnings/errors
 were generated about the plus sign being used inappropriately or anything
 else.
 
 Am I misunderstanding the documentation?  Is this possibly a bug?
 
 If this is not the way it's intended to work, could Nagios be easily enhanced
 to support this?  It seems very logical and powerful, and apparently other
 people are thinking along the same lines as I am.  I'm not using escalations,
 but a cursory read makes it appear to be supported there.
 
 Thanks in advance for any light you can shed on this!
 
 --
 Jim
 
 -
 -
 This SF email is sponsosred by:
 Try Windows Azure free for 90 days Click Here
 http://p.sf.net/sfu/sfd2d-msazure
 ___
 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


 
-- Jim




--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
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] Nagios implied and additive inheritance

2012-03-27 Thread Mark D. Nagel
On 3/26/2012 1:11 PM, Chris Beattie wrote:

 I couldn't get it to work that way, either.  Instead, I defined a 
 service escalation that activates on the first notification.  Something 
 like this might work:

 define serviceescalation {
   host_name   linux-server
   service_description 1_proc_sshd
   contact_groups  management
   first_notification  1
   last_notification   0
   escalation_options  w,c,r
 }

 I assign services to hosts with hostgroups, so I have a hostgroup_name 
 in my escalation definition instead of just a host_name.


We do something similar, but recently found that
'first_notification_delay' on hosts and services is not honored when you
handle notifications this way.  Really doesn't seem like it makes sense,
so I imagine it is just a bug.  Worked around it by having a null target
for the first escalation.

Mark

-- 
Mark D. Nagel, CCIE #3177 mna...@willingminds.com
Principal Consultant, Willing Minds LLC (http://www.willingminds.com)
cell: 949-279-5817, desk: 714-495-4001, fax: 714-646-8277

** For faster support response time, please
** email supp...@willingminds.com or call 714-495-4000


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
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] Nagios implied and additive inheritance

2012-03-26 Thread Chris Beattie
On 3/26/2012 2:04 PM, Jim Winkle wrote:
 I'd like to set up Nagios so that:
 1) In general, contact_groups for a host are notified about problems with the 
 host and any service on the host.
 2) Occasionally, we'd like other contact_groups to be notified about problems 
 with certain services on the host.

 Am I misunderstanding the documentation?  Is this possibly a bug?

I couldn't get it to work that way, either.  Instead, I defined a 
service escalation that activates on the first notification.  Something 
like this might work:

define serviceescalation {
host_name   linux-server
service_description 1_proc_sshd
contact_groups  management
first_notification  1
last_notification   0
escalation_options  w,c,r
}

I assign services to hosts with hostgroups, so I have a hostgroup_name 
in my escalation definition instead of just a host_name.

-- 
-Chris

Nothing in this message is intended to make or accept an offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
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