I'd like to hear from the Zenoss product folks on this really. I'm running Zenoss Core 2 on x86 1.2GHz with 2GB RAM and SCSI disks. This instance is only monitoring 23 devices.
You know, Zenoss is probably on the right track with the look & feel and overall functionality, but it's these little annoyances that will keep them from being widely deployed. If I'm going to be woken up in the middle of the night or bugged during a meeting by Zenoss alerting that a service is down on one of my hosts, it darn well better be down. Otherwise this is just another annoyance that I'd rather not deal with. I start to ignore the alerts all together because they come so frequently and are not accurate. Right now, I get alerts for SNMP being down/up, down/up, down/up on a few hosts. I also get the process down/up alerts for hosts where I know the process has not bounced. Someone from Zenoss please speak up here. We're evaluating Zenoss for our production and internal monitoring, alerting, event management and SLA needs but as it stands today, I can't rely on the information. ------------------------ Clayton Dillard -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=7187#7187 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
