I feel like there is more to this. If you can write something like this http://www.zenoss.com/Members/netdata/create-a-device-dependency/
How is it that we can't create a similar script that would tell the second, or third or fourth devises in a chain to not alert about anything. The problem is that this is the only example I can find and it's not well documented. I was also told this method of creating a dependency will only work within the same class. Meaning that you have to create the "transform" with in an event class. The example from the link will only work if you build your dependency in the "staus" class and then the "ping" class. So, you can't create a rule like this at the top level and then have it be inherited. In other words, the dependency will only prevent the second devise from sending an alert that it is down (because of a ping check failure) it will not prevent other checks that you may have running against the second devise. If you're still checking for mysql, for example, or really any check that does not belong to the ping status class, you'll get the other alerts. The goal is to prevent the dependent devises from sending ANY alerts. Without this ability you can page storms. It seems that given the example above, there must be away to write a script that could do this. Just need more examples, unless there is truly no way to build a dependency that can be written for the top level of /Events? -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=20210#20210 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
