If you have your traps correlating properly, I believe you should get the effect you desire with out having to override the de-duping.
Essentially the de-duping works until an event has reached a clear state (moved to history). So in the case of up/down traps if you receive down trap, followed by an up trap, the up trap should correlate itself to the down and clear the down event and move them both to history. If you receive another down trap it will not be de-duped because there is no previous uncleared matching event. To see all the up/down event you would then look in to the event history where it would display down and up event times. Normally up/down traps are only sent on state change, but if your equipment sends periodic messages when something is down then I believe you would want those messages de-duped. Because, it's not alerting that some went down, it's just indicating that it's still down. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25328#25328 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
