I believe you may have not understood (or I misunderstand) how the zEventClearClasses works - You can in the event mapping definition specify what classes clear this event (I believe that's how it works, though it may be the other way round - perhaps Matt Ray or Chet can clarify).
You can also have multiple mappings per class... ? Though there it gets wonky in my understanding as to whether being in the same class is enough to clear the event... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University nxumdon wrote, On 1/6/2009 4:46 PM: > Hi > We've got many APC UPS out in the field and they all send traps of various > types to our Zenoss system. What I'm trying to do is configure event > correlation to automatically move events to the history as they are fixed. > > For example; > > I've got an event class called UPS and in that a subclass called contacts. > I've mapped the two contact events (open and close) from one of the UPS' to > this contact subclass, set the open event to be of CLEAR status and it seems > to work just fine. > > The problem is that some UPS send contact alarms with a different OID, would > I need to duplicate this contacts subclass for this second OID? > > I'm not sure I understand how Zenoss users are supposed to use these event > classes if you have to create an entire class for each type of event you want > correlated. Not sure I understand the point of classes if each just ends up > containing one up/down (open/close, pass/fail) pair. > > Should I lump all my contact events into that one contact class, or do I have > to have seperate ones for each 'type' of contact alarm that may be sent? > > Is there no way to say, have this EVENT clear that EVENT and leave the use of > classes for management and organization of the HUNDREDS of trap types we get. > If we have to set a subclass for each pair, that is somewhere around 200+ > subclasses!!!!! > > Thanks > > J > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=29716#29716 > > -------------------- 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
