Alert Properties Actions pane

Use the Actions pane to specify alert actions.

In Alert Action, select the action to take when the alert is triggered.

Action Description
callback This connects to a TCP/IP server application and sends the alert number and message. Specify the host name and socket port number. The dialog box reconfigures for Host and Port entry.
email This is used to configure an email alert. This sends a user-defined message that is based on the alert. Use hcitcl to run Tcl scripts.
exec This runs the specified script or command in the background. The dialog box reconfigures for command entry. You can run Tcl scripts using hcitcl.
none This lets an alert fire but not run an external function run.
notify This shows a message stating the alert is triggered.
tcl This runs the specified Tcl code. Click Edit to edit existing files or procs.

Pathnames should be in the form of C:\cloverleaf\cisversion\integrator. Pathnames that include a backslash (\) are automatically replaced with a forward slash (/).

The Tcl Interpreter does not return back to hcimonitord until it is finished. This indicates that hcimonitord does not do anything until the interpreter is finished processing your code. If you think your code could block or take several seconds to run, then use the exec action.

The alert text or file name that contains the alert text can be passed to the tcl or exec actions.

%A is the message that the alert engine would send if configured to notify. Because the message contains spaces, it must be passed inside quotes so that the Tcl routine sees it as a single argument.

For example:
package require Alerts; Alerts::sendAlert "%A"

%F is the file name in the /tmp directory used by Alerts. This contains the %A message.

Update This applies the current alert action and shows them on the action list.