Here's a possible solution to this need. I hacked some code into MessageProcessor.enrich() that parses email subject lines with the following format and sets event tags accordingly:
for example: "Subject: priority=1;component=the os;severity=2" It's a real hack but it works. Only problem was that if I sent an event of, say, severity 5 (critical) and then followed up with a sev 0 (clear) when things were better it didn't move the original to history. So I researched on the forums and found what seems to be a viable solution as follows: I updated MessageProcess.py some more and allowed eventClass to be set via subject and tested with "/App/Stop" on the sev 5 failure followed up with "/App/Start" sev 0. The original critical event cleared and moved to history as desired. (I had noticed that /App/Start clears /App/Stop events via the zEventClearClasses zproperty; that's why I chose those). I would setup custom event classes to handle this event correlation for real world events. Do people think this is a sensible approach? Is someone already working on this kind of enhancement to zenmail? I really think it's needed. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=19942#19942 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
