Thanks, Matt. I would say once-per-minute is a very good starting point for Ping Cycle Time. However, I want some device classes to be pinged every 5 minutes because it's not critical to know about their status right away. Others, especially those I need to monitor closely for a while, I may want to ping every 5-15 seconds. With the current approach, this will be impossible if my Zenoss system is already on the edge of being able to ping all devices in the global ping cycle time.
My point is, I need the flexibility. I use an old 7.0 version of HP Network Node Manager now which has a lot of flexibility in this respect. Plus, it has upstream/downstream event correlation which is not even hinted at in Zenoss. I like Zenoss but I am not ready to pitch NNM for status alarming, primarily because of event correlation. Matt mray wrote: > I opened it as an enhancement. > http://dev.zenoss.org/trac/ticket/3693 > > Are there really a lot of situations where pinging more frequently is > an issue? Ping is pretty inexpensive. > > Thanks, > Matt Ray > Zenoss Community Manager > community.zenoss.com > [EMAIL PROTECTED] > -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=24738#24738 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
