Page History

...

• opEvents versions up to 2.0.3  do not support long-running programs in script actions, and opeventsd blocks until the action program terminates.
• From version 2.0.4 onwards, script action handling is asynchronous and parallel, and the event status gets updated whenever processing of a script action completes.
  Because of the asynchronous processing your action policy does not have access to any script.<scriptname> event properties.
• Up to and including version 2.0.6, script actions are excuted using the system shell.
  As a consequence you have to ensure your script arguments are shell-safe, ie. do not contain unescaped shell metacharacters (",',`,!, &...).
  This behaviour will likely change in future versions of opEvents.
• The exit code of the external program is not captured, only its output on STDOUT (and STDERR, unless the exec argument disposes of STDERR explicitely with a "2>..." construct).

• Argument substitution for event.name and node.name may need to be disabled (if your arguments need to contain a verbatim "event.sometext" string.
  This can be done by escaping the "." with an (escaped) backslash. For example

  Code Block
  arguments => 'node.host event\\.event ...and other stuff to feed the program'

  will cause the argument to contain the unsubstituted  text 'event.event'.

Configuration for email()

...