service dependency - dependent from
Christian Schneemann
schneemann at b1-systems.de
Thu Apr 8 15:55:56 CEST 2010
On Thursday 08 April 2010 03:31:03 pm C. Bensend wrote:
> >> You mean like:
> >>
> >>
> >> # All services that depend on NSClient++
> >> define servicedependency{
> >> # Host the dependent service is running on
> >> dependent_host_name HOSTNAME
> >> # Service that is dependent on the service_description below
> >> dependent_service_description C:,CPU,Dell hardware,DHCP
> >> scope,DHCP server,E:,F:,H:,I:,Shadow copies E:,Shadow copies
> >> H:,Shadow copies I:,Memory usage,SMS Agent Host,Unplanned
> >> restart,User-initiated restart
> >> # Host the master service is running on
> >> host_name HOSTNAME
> >> # Service that the others depend on
> >> service_description NSClient++
> >> # Criteria to NOT notify for, if the above service is down
> >> notification_failure_criteria w,u,c
> >> }
> >>
> >>
> >> ? Because I have several hundred dependencies configured like this.
> >
> > No, that is the way it's documented :)
> >
> > I want something like: (used other names just to make clear what I mean)
> > define service {
> > service_description nrpe
> > ...
> > }
> >
> > define service {
> > service_description filesystem_through_nrpe
> > ....
> > }
> > define servicedependency {
> > dependent_service filesystem_through_nrpe
> > dependent_from nrpe
> > }
> >
> >
> > define service {
> > service_description health_through_nrpe
> > ....
> > }
> > define servicedependency {
> > dependent_service health_through_nrpe
> > dependent_from nrpe
> > }
> >
> > or as a "better" way to define the service one is dependent from like
> > this:
> > define service{
> > service_description health_nrpe
> > dependent_from nrpe
> > ...
> > }
> >
> > like the "parent" we have at hosts.
>
> I guess I'm still not understanding what you're needing... You
> can define a service dependency for each individual service if
> that's what you're after, instead of all at once.
>
> So, if you have a service "check_linux_filesystem_nrpe" that
> depends on a service "nrpe" on a host, you can add a service
> dependency for that in its own file. Then, when you add another
> service named "check_linux_memory_nrpe" that also needs the "nrpe"
> service, you can define another, seperate service dependency for
> that in its own file. It doesn't matter if they're defined all in
> one definition or seperately, as long as your Nagios installation
> is configured to pick up on the new files it will be just fine.
>
> I hope I'm understanding you correctly?
Yes, you did. Ok, than I will do it as you mentioned here. I think that will
be the smartest solution for my needs..
Thanks.
Christian
>
> Benny
>
--
Christian Schneemann Geschaeftsfuehrer: Ralph Dehner
IT Consultant & Trainer Unternehmenssitz: Vohburg
B1 Systems GmbH Amtsgericht: Ingolstadt
Mobil: +49-(0)-1757250665 Handelsregister: HRB 3537
EMail: schneemann at b1-systems.de http://www.b1-systems.de
Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
GPG: http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0x2FA8643A41BDAB81
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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