RFC/RFP: Service parents

[lists]

You can probally ask these questions your self but...
If my understanding of this is correct, How will this work in a
templated environment?
eg Will the parent service be configured via a hostname / service name pair
Or just a service name, that Nagios will look on the applied host to find?
(I ask as we use host templates to apply service to hosts).

I am probably being very anal here, would this situation work?
Host
    |
     - service0 NRPE -->
                  -- service1 App check1
                  -- service2 App check2
    |
     - service3 HTTP check1
     - service4 HTTP check2

Could we have "HTTP check1" depend on "App check1" but not "NRPE"?

eg NRPE dies so service1 alerts are suppressed, but "service3" will
alert if needed.
    But if "App check1" fails (but not NRPE) "HTTP check1" will not alert?
--
Ritchie



On Tue, May 17, 2011 at 9:57 AM, Andreas Ericsson <ae at op5.se> wrote:
> Ahoy.
>
> This is the first of a few requests for comments and patches that
> I'll be sending out, requesting comments and patches. Please keep
> bikeshedding to a minimum.
>
> One of the more common ideas at ideas.nagios.org is to make Nagios
> easier to configure with regards to service dependencies in order
> to suppress notifications from being sent out. The most common
> case when this happens is when an agent on a monitored host goes to
> lunch but several of the checks configured for the host depends on
> that agent being up and running.
>
> The idea to easily solve such dependencies is to allow services to
> have "parents". There will be some few limitations to how these
> parents work, however, since we want to make it easy for people to
> use and we also want to make it easy to implement.
> * The parent of a service must reside on the same host as the child
>  service.
> * If the parent is in any non-ok state, notifications from the child
>  service will be blocked, but the child service check will still be
>  executed normally.
> * Internally, Nagios will create a servicedependency with a simple
>    notification_failure_criteria = ~STATE_OK
>  upon the service parent. This is necessary to avoid breaking the
>  eventbroker ABI. In Nagios 4, this can be changed, but for now we
>  remain binary compatible with current eventbrokers.
>
>
> Comments and patches welcome.
>
> --
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Tel: +46 8-230225                  Fax: +46 8-230231
>
> Considering the successes of the wars on alcohol, poverty, drugs and
> terror, I think we should give some serious thought to declaring war
> on peace.
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
>

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Nagios-devel mailing list
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel