Elmerfud, thanks for the suggestion - I had already seen that page, the problem is that I'm not clear how or whether I could apply that to our situation. My main issue is that I'm finding the concepts and interface/fields not completely intuitive, and the depth of documentation and examples not sufficient to allow someone without much time (me!) to apply it generically to their own situation.
In that page, item 8 states that correlating events will apply to all events of the same class, so applying this method for my situation I'd need a separate pre-configured class for each and every possible type of "problem" that I might receive traps for (this example relating to threads being just one)? If I don't use this method then again I need to understand how to de-deplicate or correlate based on a portion or a transform of the message string, whilst still showing the complete and latest string in the console, and how the severity parameter be excluded from consideration when de-duplicating? Could anyone talk me through in a little more detail how I might achieve what we're looking for? Thanks -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17825#17825 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
