I don't know if you can impose a throttle restriction of that nature, however you can setup device dependency so that if one failure would cascade into 30 other failures Zenoss sees secondary failures as just that secondary, and doesn't produce events on them.
I know there are posts about this all of the forums, even if I've never set it up myself. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=27617#27617 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
