question about service dependencies and templa tes
Kimmo Jaskari
kimmo.jaskari at eget.fi
Wed Feb 19 16:05:21 CET 2003
I'm also wrestling with this issue at the moment. From what I can see, there
is no way to do something like this:
define servicedependency{
dependent_host_name host_name
dependent_service_description
service_description1,service_description2, .. service_descriptionN
host_name host_name
service_description service_description
execution_failure_criteria [o,w,u,c,n]
notification_failure_criteria [o,w,u,c,n]
}
Of course, you can create one set of definitions specifying every single
service_description on one machine and then do a huge copy/paste of that
entire block, then search-and-replace the dependent_service description,
but... at this point my dependencies file is three times larger than the
entire hosts and services definition file and growing and already a gigantic
pain in the posterior to manage.
What I need is a way to do "on every host, separately make services 1, 2, 3
dependent on service X on the same host". Perfect for NRPE, to pick one
example, I want all the NRPE-based service checks dependent on NRPE itself
being up on that same machine.
Making service V on machine X dependent on service Y on machine Z is
probably useful for somebody but I can't understand why you cannot specify
multiple dependent services, as you can specify multiple machines?
> -----Original Message-----
> From: Carroll, Jim P [Contractor]
> [mailto:jcarro10 at sprintspectrum.com]
> Sent: den 18 februari 2003 18:09
> To: 'timwest at warwickshire.gov.uk'; Nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] question about service
> dependencies and templa tes
>
>
> This is something I recently decided I needed to test out
> myself. I've got
> pretty much the same setup as you. (It wouldn't surprise me
> if you had
> 10-20 service checks dependent on nrpe_active, as I do.)
>
> I can only suggest you check this out:
>
> http://nagios.sourceforge.net/docs/1_0/templatetricks.html#ser
> vicedependency
>
> I recently bounced a question very similar to yours off the
> list, without
> any helpful responses. All I can suggest is that you set up
> a trivial case
> on a non-critical machine and test it out. This is what I
> intend to do,
> when I have time.
>
> Let's make a deal: Whichever one of us tests this first,
> summarise to the
> list...? :)
>
> jc
>
> > -----Original Message-----
> > From: timwest at warwickshire.gov.uk
> [mailto:timwest at warwickshire.gov.uk]
> > Sent: Tuesday, February 18, 2003 6:50 AM
> > To: Nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] question about service dependencies and
> > templates
> >
> >
> > ***** This e-mail is communicated in confidence. It is
> > intended for the
> > recipient only and may not be disclosed further without the
> > express consent
> > of the sender. *****
> >
> > I'm using nrpe to monitor the status of various filesystems
> on several
> > machines on our network.
> >
> > I have created the following service definition
> >
> > define service {
> > hostgroup_name host_group_a
> > service_description root_filesystem
> > ...
> > ...
> > }
> >
> > and
> >
> > define service {
> > hostgroup_name host_group_a
> > service_description nrpe_active
> > ...
> > ...
> > }
> >
> > Now I want to create a service dependency for root_filesystem on
> > nrpe_active without creating a separate entry for each
> > filesystem on each
> > machine.
> >
> > From reading the documentation I can make root_filesystem
> dependent on
> > nrpe_active for all of the machines in host_group_a, but I
> > only want it
> > dependent on nrpe on the machine with the filesystem.
> >
> > The ability to add the same test to several hosts, just by
> > changing the
> > contents of the host group is great, but if I have to add a
> > separate entry
> > for the service dependency then takes that usefulness away.
> >
> > Has anyone any ideas.
> >
> >
> > --
> > Tim West, CAMS ICT Services
> > Warwickshire County Council
> > Email: timwest at warwickshire.gov.uk
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > 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:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> 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: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
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
More information about the Users
mailing list