Hi
So I've got Zenoss setup pretty sexy like and its decoding most all my traps 
and loaded most all my mibs (a few say they loaded, but show up 
empty...something to fix on a rainy day i guess), and I've got some nice 
transforms setup to fix some encoding problems and clean up some summary msgs.  

Now, what I'd like to do, if possible, is to setup a new event class, one that 
all new events would pass through before being further grouped into their more 
specific classes.  I would like this general, catch all, first class/transform 
to look at the 'evt.device' and if it falls into one subnet, change the 
component to ClientX, if it falls into another subnet, change component to 
ClientY...once the event has passed through this and been labeled (via the 
component field), it should then proceed and land in its proper event class.  

Does this make sense...is it possible?  Could I make a new Event Class Mapping 
and somehow leave it very open and generic, to catch all and only apply this 
basic 'where did you come from' transform and then pass it along.  

Thanks!
J




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=30422#30422

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to