<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1"> <TITLE>Nagios Strategies</TITLE> </HEAD> <BODY>  Hi all, I've found myself in a quandary and I'm wondering how other Nagios uses have address similar problems. We've recently upgraded to 2.6 and I've been tidying up the configs, sorting out service groups, etc. I've been adding checks for specific windows services, Exchange, Backup Exec, various MS SQL databases and that sort of thing. The more services I add, the more I consider their dependencies on each other. SNMP service is now a critical service, as without it I will get a storm of notification. I can see that service dependencies would fix this but it does seem overly complex to have to list each host/service pair in the dependency definition. One way I thought might work is to create a servicegroup called myserversnmp and add the service to the group in the service definition. Then, in the dependency definition, make that servicegroup dependent on SNMP Service on the host. This would mean I end up with a load of servicegroups, but make configuring easier as I just need to add one line per service and that's often done with copy/past/tweak. An alternative might be to regular expressions, but for me this would be an obfuscation, not really what I'm after. It would be nice if there was a service dependency directive in the service definition. How do others manage dependencies ? Thanks Matt </BODY> </HTML>