I'll just comment that it may well be a misunderstanding of mine then, but I thought I'd seen that behavior(status down suppressing other events) in 2.2.4 and 2.3.3...
I suppose event mappings would be your other choice, though hopefully other users and/or Matt Ray will comment to clear this up (and maybe I can add the answer to the Community FAQ). -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University nsalemme wrote, On 5/29/2009 2:09 PM: > I'm not sure Zen behaves the way you describe. See the example below: > > Ping Down Event Recorded: > > Device: mullin-router.* > Component: > Severity: Critical > Time: 2009/05/28 21:40:16.000 > Message: > ip 10.0.19.1 is down > Event Detail > Acknowledge > Delete > Device Events > > > Shortly after, SNMP agent down record: > > Device: mullin-router* > Component: snmp > Severity: Error > Time: 2009/05/28 21:40:24.000 > Message: > SNMP agent down > Event Detail > Acknowledge > Delete > Device Events > > > > The SNMP agent down happens after the ping down. Based off what you say > above, the SNMP agent down should be suppressed. > > I am running the latest version of Zen too, 2.4.1. > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=35432#35432 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > zenoss-users@zenoss.org > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list zenoss-users@zenoss.org http://lists.zenoss.org/mailman/listinfo/zenoss-users
