EventView

Overview:

EventView is a companion product of ClientView. EventView displays system alarms that can occur from loading software to alarms that can occur during call processing. Within EventView the alarms can be filtered to display only the type of alarm the user would like. Filtering on Severity of Alarm or entities such as Span, Channel, or general alarms are just a few. EventView also logs its information into a .csv file. The log files are located at:

 

/opt/dialogic/common/log   (Software Versions 10.5.1 - 10.5.x)

 

Launching EventView:

EventView is launched automatically when logging into ClientView. If EventView has been closed, it can be launched manually. See Below.

Launching EventView Manually:

You can launch or close EventView from within ClientView by selecting Launch EventView from the Tools menu. If the box preceding Launch EventView is checked, that signifies that EventView is already launched and displayed on Desktop.

 

sc_tree_eventview.png

 

 

EventView Windows (UnFiltered/Filtered):

Once EventView is launched the user has the ability to filter out certain events that happen. Below are screen captures of each of the tabs in EventView. (Unfiltered and Filtered). Note that in the second screen capture below (Filtered) that the General Alarms were filtered out. The General Alarms still appear in the Unfiltered Tab but will not appear in the Filtered Tab. This can be used for troubleshooting to reduce the amount of messages being logged.

EventView Main Window (Unfiltered):

sc_ev_main.png

 

EventView Main Window (Filtered):

sc_ev_main_filtered.png

 

Note: The default maximum number of events stored is 200. You can change this value with Environment variable SK_MAX_NUM_EVENTS_STORED.

 

Remove/Add EventView Alarm Fields :

Each of the columns in EventView specifies a different aspect of each alarm that is generated. As of software version 10.5.2 EventView allows the user to hide any of the columns except for the 'Descriptions' column. Simply right click in one of the heading boxes/cells and a box will appear allowing user to select or de-select which columns to be displayed/hidden. As shown above the default EventView screen has five columns. (Time, Entity, Node, Severity, and Description) the screen shot below displays the multiple selection box that appears when right clicking the heading boxes/cells.

 

sc_eventview_remove_columns.png

 

After Un-checking Severity from the multiple selection box, the EventView will hide the Severity column and resize the rest of the columns to fit the existing window size. See Below

 

sc_eventview_remove_severitycol.png

 

Below are some additional information bullets:

 

Rearrange EventView Alarm Fields:

Along with hiding the columns in EventView, the user can also rearrange the placement of the columns. To accomplish this, select the top cell of the column and drag the column to a different location in the EventView window. If EventView is closed and then reopened, the columns will rearrange themselves back to their default location.

 

Exporting EventView files:

EventView allows the user to easily export the EventView Data into a separate file. To export the data, go to the menu bar and from the 'file' drop-down menu select 'Export Alarms to Text File'. An 'Open' box will appear and allow you to browse to a directory that you would like the .csv file stored.

 

EventView Log Files:

EventView messages are logged to a comma separated file. They are written to the following location once every 24 hours.

File Location:

opt/dialogic/common/log

 

File Format:

The format of the log file is 'EventLog_xxxx.csv'. (Where xxxx is a series of numbers).

 

Displaying Individual Boxes from EventView Window:

Any of the boxes in EventView can be displayed in a Pop-Up box for easy reading.

 

For Example: Double click on one of the boxes/cells under the column heading 'Description'.  A box like the following will appear allowing user to easily read all information from that cell.

 

sc_eventview_spanfailure_popup.png

 

 

 

Interpreting Alarms

Mapping Span/Channel to VoIP Module:

Errors on a VoIP channel are reported as a span/channel. To map the span/channel to a VoIP Module/Port, see Span/Channel to VoIP Module Mapping

 

sc_ev_ip_errors.png