Event handlers provide user-defined behaviour that is to be performed upon the raising of a particular event. Events can be raised due to various system conditions (see the Events section on the general help page for more information). When this happens, associated event handlers are executed.
There are currently three types of event handlers:
The event types section arranges all available event types in the system in a tree. The Point event detectors branch
contains a list of all points (indicated with ) in the system that have event
detectors. The event detectors are listed under their respective point branches.
Event types for scheduled events, compound event detectors, and system events are listed under their respective branches. The Data source events branch contains a list of all data sources that can raise events. The events are listed under their respective data source.
To add a new event handler, click the event type that you wish to handle; the event handler details section will be
displayed. The actual event handler will not be saved until you click the icon. To
edit an existing handler, click the handler's name in the list of handlers under the event type's branch.
When you add a new handler, you must select the handler's Type. Once you save a handler, it's type is no longer editable.
An arbitrary event alias can be set by which the event handler will be visually identified. This alias is also used as the basis of the subject line for email event handlers.
To save changes to a handler, click the icon at the top right of the Event handler
section. To delete a handler, click the
icon.
Email handlers maintain up to three recipient lists. The first is the list to which a message is sent when the event is initially raised. The second is an optional list to which to send escalations. The third is an optional list sent when the event become inactive.
To add a mailing list to a recipient list, select it from the Add mailing list drop-down list and click the
icon beside the drop-down. To add a user, select it from the Add user list and
click the
icon beside the drop-down. To add a free-form email address, enter the address
in the Add address box and click the
icon beside the box. To delete any recipient
from a list, click the
icon beside the recipient. To test a recipient list,
click the
icon for the list.
To have escalation emails sent, check the Send escalation box, and enter the Escalation recipients. The escalation email will only be sent if the associated event has remained active for the Escalate if active for period.
An event inactive notification can be sent by checking the Send inactive notification box. If checked, the notification will be sent to all event recipients once the event becomes inactive. Note that, if an escalation email was not sent, the inactive notification will not be sent to the escalation list. Only those recipients that received an active notification will receive an inactive notification. This behaviour can be overridden by checking the Override inactive recipients checkbox, which allows the setting a list of specific inactive recipients. This can be useful if there are active notification recipients that should not be sent any subsequent emails (like a ticketing system).
When an event is raised, this handler will set the value of a given settable point. The Target is the settable point that will be set. Optionally, the point may be set with the value which raised the event, but this is only possible if the event was raised by a "value changed" point event detector, and the data type of the target is the same as the data type of the source. To have the target be set with the source value, check the Use source value box. Otherwise, enter the value to which to set the target in the Value to set area.
This handler will execute a local process, or shell command, optionally when an event is raised or deactivated. The respective commands can be any shell command appropriate to the host. Commands should be specified as they would be from a terminal command prompt. For very complex commands, you may find it convenient to write a shell script, and then call the script from Scada-LTS.
If a process fails to initiate for any reason, a system event will be raised providing the failure description. Also, processes will be terminated if they run for longer than 15 seconds. Non-empty standard output from the process will be written to the Scada-LTS log at an "information" level. Non-empty error output will be written to the Mango log at an "error" level.