You could just have different users with alerting rules that trigger on the various conditions... Use Count in the alerting rule definition, and figure how often they come in, and then set appropriately.
Zenoss does auto clear if the events are correlated, so alternatively, find out why the up isn't clearing the down event - see Jane Curry's paper for far more info: http://www.zenoss.com/Members/jcurry/zenoss_event_management_paper.pdf/view -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University Rudy88 wrote, On 4/7/2009 9:24 AM: > I'm fairly new to setting up Zenoss alerts and I was looking for a little > advice on how to setup alerts from SNMP Traps. > > What I would like to do: > Currently, we are monitoring several T1 interfaces on remote routers on a > MPLS network. The routers successfully send snmp trap snmp_linkDown & snmp > trap snmp_linkUp alerts just find. When a trap is sent, Zenoss detects and > then notifies via email. > > My problem: > I would like for some type of escalation. For example, if a T1 is down longer > then 3 minutes send a email to this email address. Then is that T1 is down > for 10 minutes, send a pages to this address. Zenoss seems to be sending a > alert whenever if receives the trap, almost acts as if their is no > correlation between the linkDown then the linkUP. The delay option only seems > to send the alert at the specified seconds. > > Any thoughts out there? > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=33123#33123 > > -------------------- 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
