I think the problem is your event mapping doesn't execute *because* the event doesn't have an event class key. So you have to have an event mapping on defaultmapping to catch the things *without* an event class key.
Now it would be simple if you could cascade mappings, just in default mapping set your event class key and all is good. But I don't believe you can do that yet (it is on the roadmap), so you have to do whatever you want done all in the defaultmapping event mapping you create. You'll want to sequence this before the existing default mappings I think, but use a regex or rule to only match these syslog messages (you want existing things to fall through your mapping I would expect)... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University dranch wrote, On 5/21/2009 9:02 PM: > Ok.. so I think we've come full circle. I thought I created the key in my > original post. No? > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=35104#35104 > > -------------------- 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
