I don't know about clustering, but for the zenoss autoclear, the event and clear is still in history for reference (usually). Alternatively, you could use event transforms to change the summary so the clear event doesn't actually clear it. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University
nixinfo wrote, On 12/19/2008 1:59 AM: > Hello, > > We are evaluating Zenoss in an active/passive clustered environment. The > current setup is as follows > > CentOS 4.4 > HeartBeat 2.1 > Zenoss 2.1.3 > > Since there is only one instance active at a time, we get lot of following > messages in event console, with count increasing every minute: > > ---- 8< ---- > > zenwinmodeler /Status/Heartbeat zenoss02 zenwinmodeler heartbeat > failure 28:47.0 29:47.0 2 > zenwin /Status/Heartbeat zenoss02 zenwin heartbeat failure > 28:47.0 29:47.0 2 > zentrap /Status/Heartbeat zenoss02 zentrap heartbeat failure > 28:47.0 29:47.0 2 > zensyslog /Status/Heartbeat zenoss02 zensyslog heartbeat failure > 28:47.0 29:47.0 2 > zenstatus /Status/Heartbeat zenoss02 zenstatus heartbeat failure > 28:47.0 29:47.0 2 > zenprocess /Status/Heartbeat zenoss02 zenprocess heartbeat failure > 28:47.0 29:47.0 2 > zenping /Status/Heartbeat zenoss02 zenping heartbeat failure > 28:47.0 29:47.0 2 > zenperfsnmp /Status/Heartbeat zenoss02 zenperfsnmp heartbeat failure > 28:47.0 29:47.0 2 > zenmodeler /Status/Heartbeat zenoss02 zenmodeler heartbeat failure > 28:47.0 29:47.0 2 > zeneventlog /Status/Heartbeat zenoss02 zeneventlog heartbeat failure > 28:47.0 29:47.0 2 > zencommand /Status/Heartbeat zenoss02 zencommand heartbeat failure > 28:47.0 29:47.0 2 > zenactions /Status/Heartbeat zenoss02 zenactions heartbeat failure > 28:47.0 29:47.0 2 > > ---- 8< ---- > > We have set zEventAction to drop in /Events/Heartbeat for a quick fix but > there could be some side effects since all the Heartbeat messages are now > going to be dropped. Is there any other way to fix such problem like only > dropping the message with certain string? > > > Question 2: Zenoss generates an alert everytime a threshold is breached, e.g. > filesystem usage over 75% but the alert is cleared when the problem is fixed. > Is there a way that the alert does not disappear after the problem is fixed? > > Thanks > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=29347#29347 > > -------------------- 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
