Event Log

This view contains a historical list of events (status, alarm and optionally control) that have occurred on the CommandCenter system whilst the application has been running. The data is stored and retrieved from an SQL database and can be filtered on different user criteria. This log of events will continue to grow until the maximum database size is reached. At this point data is either deleted or archived to an external file. Settings for the database can be managed in the SQL tab of the configuration dialog.

The view consists of an expandable list of events at the top of the view, A 'latest line display' will appear when the grid has been paused to view past events. This display will show the latest event to have occurred on the system.

Like each of the views it can be closed, automatically hidden using the drawing pin icon in the title bar of the view, or moved and resized to suit the current application or users preferences.

Each line of the event log shows the following parameters:

No.

This is a unique identifier number assigned when the message is received

Time This is the date and time the message was received. The time is in the form of hours:minutes:seconds:frames. The frame rate (fps) used can be configured in the Alarm tab of the configuration dialog.

IP Address

This is source of the message that has been received, normally the IP address of the frame controller containing the card.

Source Name

This string displays the xard type and user name of the card generating the message. It also adds the slot number of the device in the frame if relevant. Event Description This string displays an ASCII string of the event received. For a status update it will contain the word Status followed by the status object label and state.

Acknowledge

This displays the state of the event and can be either N/A (Not Applicable) for information messages, New (for new warning or error messages), Acknowledged (for manually acknowledged messages), Pending (for messages where the user has seen the event and is not acknowledging it until the cause is known) or Auto-Acknowledge (where no manual acknowledge is normally required) For each status object of a card type, the user can assign a status priority level to each of the states. In this way the user can determine for his system as to what constitutes an error, warning or information. This can be configured by using the Card->Configure Status Severities menu item. Warnings or errors in the system can be defined as being automatically acknowledged or not. This means that if a card status object is defined to be Auto-acknowledged a good status message will clear down the warning or error condition for this object if it exists. If the object is not Auto-acknowledged then it will not clear the error or warning state until it has been manually acknowledged by a user of the system. The right double clicking an event in this view will change the selection of the control view to the device that generated that event, giving easy navigation to the cause of the error or warning.

When over an event the right hand mouse button will bring up a list of options for the grid and event. as shown above.

Navigation

The grid will continue to update when any other events are received. This updating can be stopped by pressing the pause/start icon in the middle right hand side of the grid, you may wish to do this whilst reading or editing the list. When the pause has been pressed the navigation keys become active so that the home, end, page up and page down icons will then work as will the search and advanced filtering buttons.

Filtering (Good, Info, Warning, Error, Un-Acked, Advanced)

The items in the grid can be filtered by using the buttons to the left of the grid, de-selecting the good, info and warning buttons will mean that only the error level items are displayed. Using the Un-Acked button the grid will display only events that have not been acknowledged. Using the advanced button (only available when the grid has been paused) a dialog will prompt the user to select more complicated filters on the data viewed by the grid.

Search

This button which becomes active when the grid is paused, allows the user to search for a particular event using its ID number, or search to the event nearest a date / time specified.

Ack Grid

This button will acknowledge all the events in the view currently selected. If no filter exists then it will perform the same task as the Ack All button below. Ack All This button will acknowledge all the events in the system. This process may take a long time depending on the number of warnings / errors that have yet to be acknowledged, a progress bar will show the progress of this operation.

Event Details

Viewing details for the event will bring up the following dialog it includes the parameters above as well as details of the card ID and who acknowledged the error. The free format notes field allows the user to add relevant information into the system to describe the cause and actions taken. If information has been entered in the Notes field


© 2014 Grass Valley USA, LLC. All rights reserved. Grass Valley is a registered trademark of GVBB Holdings S.a.r.l.