Configurable Actions

In this dialog box you can set which action is to be executed when a condition is met.

action_create_dialog

The configurable actions are divided into two different categories: Actions that notify one or more persons and actions that actively solve a problem.

The following actions are available:

•	Notification:

•	Send a notification via email

•	Send an SMS/Text

•	Create an acoustic Warning/Notification signal

•	Create a warning speech

•	Create an entry in the Windows Event Log

•	Set the status of an USB signal light

•	Send notification via Net Send

•	Suppress the execution of further actions

•	Set the Status

•	Do not save collected data

•	Counteractions:

•	Execute a process on a remote system

•	Manage a system service

•	Power On/Off a switchable power strip

•	Set a SNMP value

•	Execute a script or program

Please note: The chosen action will only be performed where the ServerSentinel process is executed. This is not necessarily your current computer! In fact, if an acoustic signal is to be used as a problem notification, it may not be in hearing range. In such a case, you may overhear the warning tone / notification!

The use of variables:

When an action is performed it notifies the user of the particular state of the system. In most cases a message is generated.
ServerSentinel allows the use of text variables that contain information of the current status.

These variables are accessible via the assistant forms that are displayed if an action is configured. Most of them are
specific to the context of the sensor the action is configured in. So be careful if you use an action for different types of sensors,
as some variables might be invalid for a particular sensor.

The following variables are usable and valid for every sensor:

General Variables
[$SensorData$]	This is the default. It generates an overview of all the data that is collected by the particular sensor.
[$Time$]	This variable is replaced by the current time
[$Date$]	Represents the current date
[$DateAndTime$]	A date and time string defined by RFC 1123, e.g.: Mon, 08 Jun 12:30:59 GMT
Data-related Variables
[$CheckTime$]	The time the check was performed
[$ResponseTime$]	The time that elapsed during the check operation, this can be zero e.g. for event based sensors
[$StatusFlag$]	The status indicator, Ok, Warning or Error
[$Status$]	A status string that among other things indicates whether an action took place when a condition evaluated to true
[$ExceptionInformation$]	Information string of a possible exception
Sensor configuration variables
[$Name$]	The name of the Sensor as defined by the user
[$Description$]	The description string
[$CheckInterval$]	The configured check interval, this value is not in use for event based sensors
[$Information$]	Sensor information as displayed in the "Information" column of the sensor overview in the main window of the graphical user interface
Condition Variables
[$ConditionName$]	The human readable name of the data property as configured in the condition editor
[$Operator$]	The operator to use, e.g. 'equals', 'is lesser than' or 'contains'
[$Value$]	The constant value that is used to check whether the condition evaluates to true