gcarter wrote:
> I utilize the evt.resolution and evt.explanation fields for this. Generally,
> I set them in the appropriate event class transform.
Thank you, that seems to work just fine. I'll be able to pass instructions to
my operators using this.
I do want to make sure that what I'm seeing is expected behavior and that I can
expect the behavior to continue as Zenoss is upgraded. Can anyone comment?
In a transform, it looks like you can use any evt. variable you want:
Code:
evt.explanation = "Test Explaination"
evt.ops = "Test evt.ops"
evt.anyOldThing = "Test Any Old Thing"
These fields will appear on the event's Detail tab with the expected field name
(explaination, ops, anyOldThing).
Code:
Field Value
anyOldThing Test Any Old Thing
explanation Test Explaination
ops Test evt.ops
But when I retrieve the event in zendmd, the fields (explaination, etc.) aren't
there. However, the information is all available in the evt._detail variable
(which is a list).
Code:
>>> print evt._details
(('anyOldThing', 'Test Any Old Thing'), ('explanation', 'Test Explaination'),
('ops', 'Test evt.ops'))
>>> print evt._details[1]
('explanation', 'Test Explaination')
>>>
As long at that's the way it's supposed to work, I can use it. Just hate to
build on something that's not designed behavior.
Thanks,
Larry
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=35486#35486
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users
