Notifier Setup Tab

Notification Type

Select the output type for the notification in this drop-down list. See the detailed descriptions of the notification types in the section below, Notification Type Configuration.

Duplicate Suppression (sec)

Enter the number of seconds during which an identical event is suppressed from being logged. The default value is 0.

Base Configuration

The Base Configuration settings vary depending on the selected notification type and can be the location of a log file, database profile, or credentials, etc. See the respective notification type descriptions below for more information.

Target Field Configuration

These settings are used for constructing the content of the notification, and they vary depending on which notification type you have selected, see information about each notification type below.

Database

Browse and select the database profile defining the database in which the table resides, see Database Profile for information about how to define a Database profile. 

SQL Statement

Type in any SQL statement, using '?' for variables which are to be mapped against event fields in the Event Setup tab. Trailing semicolons are not used. In the case of running several statements, they must be embedded in a block.

Directory

Enter the path to the directory where the file in which events are to be logged resides.

Filename

Enter the name of the file in which events are to be logged. In case the file does not exist, it will be created when the first message for the specific event map arrives. New messages are appended.

Size

Select this check box to define the maximum size of the file. When this parameter is exceeded, the existing file is renamed and a new one is created upon the arrival of the next event.

The old file will receive an extension to the file name, according to <date_time_milliseconds_timezone>.

Time

Select this check box to define the maximum lifetime of a file before it is rotated. When this parameter is exceeded, the existing file is renamed and a new is created upon the arrival of the next event.

If the time is set to rotate every:

• hour, rotation is made at the first full-hour shift which is xx:59.

• 2 hours, rotation is made in predefined two-hour intervals (0,2,4...22) when turning to the next full hour. For example after 01:59.

• 3 hours, rotation is made in predefined three-hour intervals (0,3,6, ...21) when turning to the next full hour. For example after 02:59.

• 4 hours, rotation is made in predefined four-hour intervals (0,4,8, ...20) when turning to the next full hour. For example after 03:59.

• 6 hours, rotation is made in predefined six-hour intervals (0,6,12 ...21) when turning to the next full hour. For example after 05:59.

• 8 hours, rotation is made in predefined eight-hour intervals (0,8,16) when turning to the next full hour. For example after 07:59.

• 12 hours, rotation is made at high noon and at midnight.

• day, rotation is made at midnight.

• week, rotation will be done at midnight on the last day of the week.

• month, the rotation will be done at midnight on the last day of the month.

The old file will receive an extension to the file name, according to <date_time_milliseconds_timezone>.

If both Size and Time are set, both behaviors apply.

Separator

Select how to separate logged events from each other. Valid options are:

• Linefeed

• CR + LF (Carriage return + Linefeed)

• Comma

• Colon

• (None)

Log Line

Enter the text to go into the log file.

For further information about how to obtain the text, see Target Field Configuration below.