Alert configuration options
This tab is where you can configure alert-related preferences.
This table shows the available options on the Alert Configuration tab:
Option | Description |
---|---|
Global Polling Interval | The global polling interval helps in diagnosis and tuning of the
monitor daemon. The global polling interval affects the monitoring updates to the Network Monitor. Extending the polling interval means that the polling interval is the de facto minimum duration. For example, the polling interval is 5 minutes, but an alert is defined with a duration of 30 seconds. The alert does not fire until the next interval, which is 5 minutes. The default value is 5 seconds. The minimum interval is 5 seconds and the maximum interval is 5 minutes. Values greater or lesser than these cause an error. |
Email action options |
Email options can be predefined though the Site Preferences dialog box. This reduces the requirement of specifying them every time when configuring the email action on the Alerts dialog box. Predefined values are only used when these options do not have specified values in the current alert.
In the Alert Configurator, separate multiple entries in the To and Cc fields with a comma. For example, someone@domain.com,person@thedomain.com,support@yourdomain.com. |
Click this to test whether the currently configured email settings are
valid. This opens the Test Email
Settings dialog box, where you specify the address and
message body of the test email. The Test email Alert supports global variables. The IDE replaces the global variable with the real value before sending the test email. |
|
By default, alert email messages list all thread information in the source. Select this option to only list the threads that meet the criteria. | |
Select this to write alert events to an external database (SQLite)
instead of the alert log file. A SQLite database is generated under $HCISITEDIR/exec/hcimonitord/alerteventlog.sdb. Every triggered alert is logged in the table of this database. Any SQLite administration tool can access this database file. In Cloverleaf, this database/table is used most often by Global Monitor for end-user visualization on alert logging. This also saves events without a notify alert action. |
|
Select this to configure the default alert file that Monitor Daemon uses when starting. Only one file can be configured. The default file is default.alrt. When this is
selected, |