thanks, that's interesting stuff, and may come in handy. but again i come back to the issue i reported. this is an instance of zenoss thinking a process is down when it isn't. i'd like to use zenoss process monitoring. the idea here is to have a one-stop-shop for all of this - the fewer separate bits and pieces strewn around, the better.
since i assume that zenoss is using snmp to determine whether processes are up or down, this also strikes me as being at cross purposes. the last thing i want is to have events 'alerted very quickly' - if those events are incorrect! that's one of the features of the zenoss process monitoring that would be appealing if it worked - the ability to have a process report an error, but if it resolves itself within a few minutes, have it not alert me. that worked fine in the instance of 'memcached' that i mentioned in my message yesterday - zenoss thought it was down (though it wasn't) but it detected a couple of minutes later that is was actually up - and cancelled alerting for it, so i didn't get paged about that one. the mongrels however - configured identically in zenoss - it thought they were down too (they weren't) but it failed to automatically detect that they weren't down a minute later. so i got paged. i guess i'd just like to understand this inconsistency, and whether i'm configuring something wrong, or whether it's a bug. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22235#22235 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
