You know, I think it has to have something to do with the environment. I
haven't had much/many of the issues posted. So far, I've dealt with
transient alerts by incrementing the count to >1 for an alert to
trigger. This doesn't cause any major delay for us, but totally got rid
of the "false alerts", which seem to actually have been indicative of
transient network errors.
WMI monitoring has been working fine for me since 1.1.1 once I figured
out how to set it up. In fact, the only current bug I have is with
subclasses of /Server/Windows (which I've reported), and I can work
around that by putting devices in /Server/Windows if I need service
alerting.
One thing I'm not doing is using the Virtual Machine provided. I think
it's not intended for production use, and several reported issues seem
to occur in the VM, but not on CENTOS5, for instance.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
bnice wrote:
WMI errors are not the only problems I get with zenoss. I also get many false
positives (switches are marked as down but they're running, problems with snmp,
wrong performance for accesspoint interfaces).
I set up nagios a few days ago, and everything works fine with it (currently
monitoring with icmp, snmp and some services (http, smtp, pop3). It's more work
to include all hosts, but it runs fine.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=16982#16982
-------------------- m2f --------------------
_______________________________________________
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
