Grass Valley iControl V.4.43 - Manual (Page 115)

Logs
Summary
Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Working with Event Log Viewer and Incident Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Working with Loudness Logger and Loudness Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Creating, Viewing, and Deleting Channel Performance Reports . . . . . . . . . . . . . . . . . . . . . 223
Key Concepts
Event
An event in iControl is any occurrence that changes the condition of a monitored element, for
example:
• a change in alarm status, including updates to status text
• an acknowledgement
• a change in an alarm’s latch status
• a change in an alarm’s mode (offline, in maintenance, or online)
• the creation or deletion of a virtual alarm
• the addition or removal of a device
• execution of a script (if the script supports logging)
• a router crosspoint change
Incident
An incident is a grouping of related iControl events. Incidents make it much easier to extract
useful information from iControl. Instead of looking for answers in a large list of alarm events,
you can have events automatically correlated and grouped into manageable incidents,
making it easier to explore the current status of a problem, its root cause, its duration, or its
resolution.
Note: Not all events are associated with alarms. For example, if a device driver
triggers a reboot, this event might be recorded in the log database with a timestamp,
device name, text message, etc., but with no associated alarm information.