NV, want to put this on the Wiki?
A sequence is just 2 or more mappings with the same event class key.
They are applied in order of priority(managed by the Sequence tab inside
the mapping).
Rules are python expressions that return true or false.
A true will cause the zProperties and transforms of that mapping to
apply, and the event processing will not continue to the next sequence.
A false return value will cause the event to continue to the next
mapping in sequence.
This isn't explained this well in the Admin Guide or the Zenoss Book IMO
- I finally understand better what a rule ought to be (and what matching
language . . .).
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
nv wrote:
Ok.. I think I know what you are trying to do now. In my opinion, the transform is the wrong place to try and map 2 different events(With the same eventClassKey) into 2 differnet severities. You should use 2 mapping of the same eventClassKey in sequence and use the "rule" python expression to determine which one to apply.
A sequence is just 2 or more mappings with the same event class key. They are
applied in order of priority(managed by the Sequence tab inside the mapping).
Rules are python expressions that return true or false.
A true will cause the zProperties and transforms of that mapping to apply, and the event processing will not continue to the next sequence.
A false return value will cause the event to continue to the next mapping in sequence.
guyverix wrote:
Grin, I am making it too complicated, huh? I can believe that. Thanks for the python links, I am going to be checking those out today. If I can get that silly %!$#@ transform to work, I will put up a generic on here for others to use as well. I know people have had problems with SNMP traps with the same OID being used for both set and clears. This hopefully will take care of that.
The simple transform that was listed above does work by itself, but when I do
the full transform with two return values, apSysMgmtSAHostname and
apSysMgmtSAStatus it no longer works unless I do the str, rather than the
getattr function for the Status value. I will probably try to reverse this,
and if necessary use getattr for Status, and str for Hostname, if i really need
them both in my event transform. (Gotta make sure it is clear for my techs in
the trap data, somehow).
Thanks for pointing me in another direction to take this.
Chris.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=24282#24282
-------------------- 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
