Intelligent way to apply MANY service dependan cys?

[Ben Conrad]

I think you will want to look at 'service cluster monitoring'
 
http://nagios.sourceforge.net/docs/2_0/clusters.html
<http://nagios.sourceforge.net/docs/2_0/clusters.html> 
 
 

-----Original Message-----
From: Ray Ward [mailto:ray.ward at mapfusion.com]
Sent: Friday, June 24, 2005 2:13 PM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Intelligent way to apply MANY service dependancys?



Hi, I have been using Nagios for a long time but have just switched to
Nagios v2.0b3 and I'm re-working my config files a little bit. A large
portion of my monitoring is done via the NRPE plugins. And a large portion
of the NRPE checks are common across all of the machines. So my structure is
as follows...I have all of the Sun servers in a hostgroup SUN-Servers, I
have definitions for about 8 common NRPE checks that are assigned to the
SUN-Servers hostgroup. So far so good, with very little in the way of
definitions I have 100's of checks defined. Now to my problem, I would like
to define a service dependancy for all NRPE services to be dependant on one
check_nrpe_daemon check. So when the daemon is down I don't receive multiple
alerts for every NRPE check. So I'd like to get the equivalent of this:

define servicedependency{ 
        dependent_host_name             DBDEV 
        dependent_service_description   / Root Slice 
        host_name                       DBDEV 
        service_description             Check NRPE 
        inherits_parent                 1 
        execution_failure_criteria      o,w,u,c,p 
        notification_failure_criteria   o,w,u,c,p 
} 

For every common NRPE service for every host in the SUN-Servers group. Now
if I use the SUN-Servers hostgroup in the servicedependency definition it
makes every NRPE service dependant on EVERY host's NRPE Daemon...this
obviously isn't what I want. The best solution I have to this problem is to
NOT send notifications for UNKNOWN service checks for every NRPE check
except the daemon check. But I'd like to know if there's a better way to
apply service dependany's in this situation. Thanks in advance for any help.

PS. Below I've included the relevant entries for one host/NRPE check
definitions. 

Ray, 




define service { 
        use                             generic-diskcheck 
        hostgroup_name                  SUN-Servers 
        service_description             Check NRPE 
        check_command                   check_nrpe_daemon 
} 

define service { 
        use                             generic-diskcheck 
        hostgroup_name                  SUN-Servers 
        service_description             / Root Slice 
        check_command                   check_nrpe!check_disk1! 
} 

define service{ 
        name                            generic-diskcheck 
        use                             generic-service 
        is_volatile                     0 
        check_period                    24x7 
        max_check_attempts              3 
        normal_check_interval           10 
        retry_check_interval            1 
        contact_groups                  office-admins 
        notification_interval           1440 
        notification_period             8x5 
        notification_options            w,u,c,r 
        register                        0 
} 

define service{ 
        name                            generic-service 
        active_checks_enabled           1 
        passive_checks_enabled          1 
        parallelize_check               1 
        obsess_over_service             1 
        check_freshness                 0 
        notifications_enabled           1 
        event_handler_enabled           1 
        flap_detection_enabled          1 
        process_perf_data               1 
        retain_status_information       1 
        retain_nonstatus_information    1 
        register                        0 
        } 

define hostgroup{ 
        hostgroup_name  SUN-Servers 
        alias           All SUN Solaris Servers 
} 

define host{ 
        name                            generic-dev-host 
        parents                         MFSW_SVR01 
        notifications_enabled           1 
        event_handler_enabled           1 
        flap_detection_enabled          1 
        process_perf_data               1 
        retain_status_information       1 
        retain_nonstatus_information    1 
        check_command                   check-host-alive 
        max_check_attempts              10 
        notification_interval           60 
        notification_period             8x5 
        notification_options            d,u,r 
        hostgroups                      DEV-Servers,Office,SUN-Servers 
        contact_groups                  office-admins 
        register                        0 
        } 

define host { 
        use                     generic-dev-host 
        host_name               DBDEV 
        alias                   Development ColdFusion & Oracle 
        address                 dbdev.mapfusion.com 
} 

_______________________________ 
Ray Ward 
System Administrator 
MapFusion Technologies Inc. 
 <mailto:ray.ward at mapfusion.com> mailto:ray.ward at mapfusion.com 
 <http://www.mapfusion.com/> http://www.mapfusion.com 
_______________________________ 
NOTICE: 
This message is intended only for the use of the individual or entity to
which it is addressed; and it, including any attachments, may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If the reader of this message is not the intended
recipient, or the employee or agent responsible for delivering the message
to the intended recipient, you are hereby notified that any disclosure,
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please delete
it from your system without copying or forwarding it and notify us by
telephone (905-709-1925) or by return e-mail immediately. MapFusion Corp.
and its affiliated companies do not accept responsibility or liability for
any loss or damage arising in any way from your receipt or use or for any
errors or omissions in the contents of this communication. 




______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20050627/d24b9665/attachment.html>