jcurry
2012-12-13 10:49:48 UTC
jcurry [http://community.zenoss.org/people/jcurry] created the discussion
"Care with creating new triggers!!"
To view the discussion, visit: http://community.zenoss.org/message/70529#70529
--------------------------------------------------------------
If you create a new trigger, you supply the name and the trigger is added. You are not immediately taken into an edit panel.
WARNING, WARNING!!!
This trigger, by default IS enabled and has a filter of DevicePriority =Â Â Â Â Â Â Â Â Â Â
with no value supplied. This is not legal.
On its own, this isn't an issue. If this trigger is then used as part of an enabled notification, you get error messages in zeneventserver.log like:
2012-12-13T10:26:43.334 [INDEXER_EVENT_SUMMARY] WARNÂ org.zenoss.zep.impl.TriggerPlugin - syntax error exception raised while compiling rule: , SyntaxError: ("no viable alternative at input '\\n\\n'", ('<string>', 1, 34, 'lambda evt, dev, elem, sub_elem : \n'))
Unfortunately this doesn't tell you which is the bad trigger.
Moral of story - ALWAYS edit a new trigger when you create it and make sure it is legal.
I think that an enhancement request is required such that a new trigger is disabled by default (this is the default with notifications).
Cheers,
Jane
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70529#70529]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Care with creating new triggers!!"
To view the discussion, visit: http://community.zenoss.org/message/70529#70529
--------------------------------------------------------------
If you create a new trigger, you supply the name and the trigger is added. You are not immediately taken into an edit panel.
WARNING, WARNING!!!
This trigger, by default IS enabled and has a filter of DevicePriority =Â Â Â Â Â Â Â Â Â Â
with no value supplied. This is not legal.
On its own, this isn't an issue. If this trigger is then used as part of an enabled notification, you get error messages in zeneventserver.log like:
2012-12-13T10:26:43.334 [INDEXER_EVENT_SUMMARY] WARNÂ org.zenoss.zep.impl.TriggerPlugin - syntax error exception raised while compiling rule: , SyntaxError: ("no viable alternative at input '\\n\\n'", ('<string>', 1, 34, 'lambda evt, dev, elem, sub_elem : \n'))
Unfortunately this doesn't tell you which is the bad trigger.
Moral of story - ALWAYS edit a new trigger when you create it and make sure it is legal.
I think that an enhancement request is required such that a new trigger is disabled by default (this is the default with notifications).
Cheers,
Jane
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/70529#70529]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]