Re: [Nagios-devel] Implied/Additive inheritance
-
Guest
Re: [Nagios-devel] Implied/Additive inheritance
> -----Original Message-----
> From: John Moody [mailto:[email protected]]
> Sent: Thursday, July 08, 2010 5:22 PM
> To: [email protected]
> Subject: Re: [Nagios-devel] Implied/Additive inheritance
>=20
> Gius, Mark createspace.com> writes:
>=20
> >
> > Although the documentation does not make this clear, implied and
> additive
> inheritance applies to many
> > other objects and directives. I'm personally using it on hostgroups,
> contact_groups, contacts,
> > service_groups, etc. I believe that any directive that can be
> defined as a
> series of comma-delimited
> > strings will support the additive/implied inheritance syntax,
> although I would
> confirm on anything I
> > didn't mention previously, since I don't know for sure.
> >
> > -Gius
> >
> > > -----Original Message-----
> > > From: Thomas Guyot-Sionnest [mailto:dermoth aei.ca]
> > > Sent: Thursday, July 08, 2010 4:26 AM
> > > To: nagios-devel lists.sourceforge.net
> > > Subject: Re: [Nagios-devel] Implied/Additive inheritance
> > >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On 10-07-08 05:44 AM, john moodysrus.com wrote:
> > > > Hey Team,
> > > >
> > > >
> > > >
> > > > I am having trouble combining 'Implied' and 'Additive'
> inheritance
> > > for
> > > > normal service notifications. The documentation implies the
> ability
> > > to
> > > > combine 'Implied' with 'Additive' inheritance is restricted to
> > > > escalations, is this correct? If so, can I suggest this **very**
> > > > powerful option be expanded to work with normal service
> > > notifications?
> > > >
> > > >
> > > >
> > > > The scenario is the primary contact_group ('+support_team' for
> > > example)
> > > > is set at the host level. This group is nicely inherited by all
> the
> > > > services on that host (very cool). If we add a contact_group
> > > > ('+developers' for example) to an individual service on that
> host,
> > > the
> > > > primary_contact group information is overridden, and only the
> > > > 'developers' are contacted.
> > >
> > > +1... I have the same issue and I reported it a while ago. I don't
> > > think
> > > the fix would be so hard, but I haven't had the time to really look
> > > into it.
> > >
> > > FWIW I also suggested generric templates, because some of my
> additive
> > > templates contains instructions that can be used at multiple places
> (ex
> > > hostgroups that can be added to service templates, service
> > > dependencies,
> > > etc.
> > > http://ideas.nagios.org/a/dtd/18864-3955
> > >
> > >
> > > - --
> > > Thomas
>=20
> Thanks guys for the quick responses!! I have thrown in an example
> below (partly
> stolen from the docs) to clarify the issue (my written example may not
> have been
> clear).
>=20
> define host{
> name linux-server
> contact_groups linux-admins
> ...
> }
>=20
> define service{
> host_name linux-server
> contact_groups +management
> ...
> }
>=20
> This results in only the 'management' team receiving notifications but
> the
> implied/additive *does* work as advertised for escalations. I am
> attempting to
> leverage the escalation function as a work around at present, but it's
> not
> pretty.
>=20
> cheers
>=20
Ah, I misunderstood what you were trying to do. I see the same behavior, w=
here a contact_group defined by the host is not picked up by the service. =
It appears as though implied/additive is a behavior specific to escalations=
.
I just verified that the additive inheritance works for service uses servic=
e on contact_groups, so you may be able to get something to work there (it =
wouldn't be clean though). Alternatively, if you set contacts (not contact=
_groups) on a host, when you add contact_groups to the services, those defa=
ult contacts will _not_ be overwritten. You'll then have to specify contac=
ts null anywhere you really don't want the default contacts specified in th=
e host to be notified.
And as another alternative, our configs only make use of the default contac=
t for hosts/services as a failsafe. We
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]