Grass Valley iControl V.6.02 - Manual (Page 139)

iControl
User Guide
129
Alarm Configuration for Event Logging
By default, all alarm events in iControl are recorded in the log database (when logging is
enabled). You can, however, change the default settings. For individual cards, this is done by
opening the card’s control panel (see
"Control Panels and Device Parameters" , on page 203).
URL The location of the remote database—this value is automatically filled in based on the
values in the Type and Host fields, but can be edited.
User Enter a valid user name for access to the remote database.
Password Enter a valid password for access to the remote database.
--- Advanced Options ---
Enable event log Select to have the GSM begin recording events in the log database.
Enable incident log Select to have the GSM begin recording incidents in the log database.
2
Create an incident for each
alarm automatically Select to generate a new incident for each alarm whenever its status changes to minor,
major, or critical. When this option is checked, the Incident Viewer becomes a global viewer
for all current faults in the current GSM.
3
Clear resolved incidents
automatically after Select to automatically clear an incident if it has been resolved for the specified amount of
time.
4
1. Support for MySQL has not yet been implemented.
2. The incident log depends on the event log, so both options must be enabled.
3. This option is selected by default.
4. When an incident is cleared automatically, the corresponding alarm latch is also reset, which is not
desirable in most situations. As of iControl version 3.31, this option is not selected by default. This
does not affect existing configurations.
(Continued)
Interface Element Description
A check mark indicates
events associated with the
alarm will be logged