On Monday 27 April 2009 11:05:39 Frank Altpeter wrote: > Hi list, > > I need a little input on a configuration problem. I've got a list of > hosts, which are running NRPE to check local services. So, if the nrpe > daemon on one of these hosts stops working, I get alarms for every > configured nrpe-check. Now I thought that the service dependency would > be the configuration of my choice to suppress multiple alarms. But I'm > a bit confused how to configure this correctly. > I'm checking the nrpe service itself on these hosts, and want to > suppress alarms for the other nrpe-based services if the nrpe check > fails. Is there a way to configure this in an optimized way, without > having one servicedependency block for each host and each nrpe check ? > As far as I understand servicedependency config, there can be multiple > hosts as dependent, but only one dependent service with one depending > host and service, which would be a pain to configure with 130 hosts :) > > I would imagine doing something like that (for example): > > # Suppress notifications for nrpe-based services if nrpe check itself fails > define servicedependency { > host_name * > service_description NRPE > dependent_host_name $self > dependent_service_description DISKS,SWAP,USERS > execution_failure_criteria w,u,c,p > notification_failure_criteria o,w,u,c,p > }
What you want is like what you put in the example above but you want to change it to define servicedependency { host_name * service_description NRPE dependent_host_name * dependent_service_description DISKS,SWAP,USERS execution_failure_criteria w,u,c,p notification_failure_criteria o,w,u,c,p } also you may want to change the notification criteria to a more suitable like c,w,u ( that means in the case of the NRPE being critical , unknown, or warning , you will not get a n alert) . you can also do it with hostgroups define servicedependency { hostgroups_name group1,group2 service_description NRPE dependent_hostgroups_name group1,group2 dependent_service_description DISKS,SWAP,USERS execution_failure_criteria w,u,c notification_failure_criteria o,w,u,c } Assaf IMPORTANT . this email and the information in it may be confidential, legally privileged and/or protected by law. It is intended solely for the use of the person to whom it is addressed. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Please also delete all copies of this email and any attachments from your system. We cannot guarantee the security or confidentiality of email communications. We do not accept any liability for losses or damages that you may suffer as a result of your receipt of this email including but not limited to computer service or system failure, access delays or interruption, data non-delivery or mis-delivery, computer viruses or other harmful components. Copyright in this email and any attachments belong to Select Service Partner UK Limited. Should you communicate with anyone at Select Service Partner UK Limited by email, you consent to us monitoring and reading any such correspondence. Nothing in this email shall be taken or read as suggesting, proposing or relating to any agreement concerted practice or other practice that could infringe UK or EC competition legislation. Select Service Partner UK Limited is a company registered in England and Wales (company number 05687183) whose registered office is at 1 The Heights, Brooklands, Weybridge. Surrey. KT13 0NY ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ 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