<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> (This was previously posted in nagios.users. This might be a better place) Hi list, I think host and service dependencies are a great help in accurately defining a problem. I even think they are even indispensable to reflect truly accurate reporting/alarming for complex environments with different teams being responsible for different systems that depend upon each other. But I'm missing 2 things in Nagios: <ul> <li>When service1 is dependent upon service2, and service2 is critical it would be really helpful if the critical status of service1 reflects something like: "Service2 dependency failure". This way, when I'm responsible for this service/host, I know with just an SMS that it's someone else that needs to fix the problem. I know you can repress the notifications for service1 in this case but sometimes you just want to know what's going on. </li> <li>You can't track service and host dependencies from the web interface. It would be extremely helpful to have besides a "status map" a "dependency map" (with recursive dependencies resolved). I have no problem with the config files, but tracking dependencies in large setup can be tedious. </li> </ul> What are your thoughts? Js </body> </html>