Making settings
4.3Making settings
In the General Settings screen you can define general settings for alarm handling.
You can define the actions to be executed by default and regardless of the alarm groups whenever an alarm arrives.
You can define the following actions:
–Alarms relating to failed authentication are suppressed.
–Alarms from server blades are issued with the relevant name of the blade server.
For different error severities you can specify the following actions. Any combinations are possible.
–The alarm is to be written to the operating system
When you receive alarms with the checked severities, the alarms are logged in the operating system event log.
–When you receive alarms with the checked severities, a
–The Alarm Monitor window is to move to the foreground.
Every time you receive an alarm with the checked severities, the AlarmMonitor window is displayed on top of any open windows. For this to happen, the AlarmMonitor window must be open already.
You can specify when the alarm is to be deleted. You can define whether the alarm is to be deleted when it reaches a certain age or when the log list contains a certain number of entries. Once a certain number of entries is reached, the oldest one in the list is deleted.
Clicking the Apply button saves the new settings. Clicking the Reset button restores the settings from the last save.
IWith general settings, event logs are recorded independently from Alarm Rules. Depending on the configuration, two event logs may be recorded for the same alarm.
58 | ServerView Event Manager |
