One other thing that would be nice is some better way of handling
transient downs. I have played with count, and delays, but still get
daily random TESTPC SNMP is down, and one minute later TESTPC SNMP is
up... It seems that occasionally CPU load will cause the SNMP agent to
not respond to one query, but then to be back up for the next.
Now, I'm not saying that we should make it impossible for Zenoss to
detect that a server has a flaky SNMP response, but it should also be
possible to clearly *tune* what we consider a flaky response for a
server. I had hoped that setting it to 2 or 5 in count would limit
alerts, but it doesn't seem to work for me, unless Zenoss is by default
polling multiple times a minute. I'm almost sure some of this is
documentation (I'm not building my alerting rules correctly)...
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
Erik Dahl wrote:
On Jun 26, 2008, at 9:21 PM, mwcotton wrote:
My apologies for the tone [Embarassed]
but I would love one software package that under promises and over
delivers. The concept of Zenoss is awesome, and the implementation
could be beautiful. but........
No worries we have thick skin. :) We have heard loud and clear that the
next release needs to focus on stability, especially WMI, and that is
the focus.
-EAD
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
