Analyzing Server Activity

You can use the Server Log pane in the diagnostics section of the Web Console to view the current or prior server activity log (edaprint.log) from either a management perspective (Session and Connection activity) or a raw version of the log with or without filtering for certain components and IDs. By default, the Server Log chronologically records all server activity from the time the Workspace Manager was started. It contains basic activity information, as well as server start up information and IBISNAP and shutdown information. IBISNAP is a snapshot of the server environment showing various usage statistics, and listener and agent status. If an abend occurs, the snapshot contains additional debugger stack information that aids the Customer Support Services staff in determining the problem.

You can view the first 50,000 lines of the log file from the Web Console. If you wish to view lines beyond 50,000, you can open or save the file in a text editor.

Procedure: How to Access the Server Log Files

From the Workspace menu, select Configuration/Monitor.
Expand the Logs and Traces folder in the navigation pane.
Right-click Workspace Logs and select View.
The Workspace Logs page opens.
Right-click hliprint.log and select View
or

Right-click edapring.log and select a report type:
- Full Report has View and Open or Save options.
- Connection Report has Detail, Summary and Graph options.
- Page Hit Report has Detail and Summary options.

The log opens in the right pane.

Procedure: How to Filter the Server Log

From the Workspace menu, select Configuration/Monitor.
Expand the Logs and Traces folder in the navigation pane.
Right-click Workspace Logs and select Filter.
The EDAPRINT Log Filter page opens.

Select an option from the Select Filtering drop-down menu.
Click Set Filter.
If you choose Filter by Category, the following page opens. Set your filtering parameters and click Set Filter. For any item, clicking the check box without an entry in the input box filters on all items of that type. If you also enter a specific value in the input box, that filter will be executed. (For example, you can request filtering on all users, which defaults to *, or an individual user.) You can combine items from the list, mixing all of items of a type with specific items, as needed.
If you choose Filter by Category, the following page opens. Enter From timestamp and To timestamp information and click Set Filter.
Right-click Workspace Logs and select View.
The Workspace Logs page opens.
Right-click edapring.log and select a report type.

Procedure: How to Control EDAPRINT History From the Web Console

From the Workspace menu, select Configuration/Monitor.
Expand the Logs and Traces folder in the navigation pane.
Right-click Workspace Logs and select Properties.
The Event Logging Properties page opens.
Enter values for:
email_suppress_interval

Suppresses duplicate e-mail notifications if the same event occurs again during this time interval. The default is 600 (10 minutes).

edaprint_history

Defines the number of saved edaprint.log files to keep. The default is 5.

edaprint_max_lines

Defines the maximum number of lines for each edaprint.log before it is archived and a new edaprint log is started.

edaprint_max_days

Defines the maximum number of days, starting from the time the server is started, for each edaprint.log before it is archived and a new edaprint log is started. Note that the new edaprint.log file will only be created after the edaprint_max_days value has been exceeded and a connection event has occurred (that is, if the server is idle, the new edaprint.log file will not be created until a connection request is received). For related information, see Controlling EDAPRINT History.

edaprint_ipname

Determines if the server should convert IP host addresses to names. This requires DNS lookups. The default is n.
Click Save and Restart Server.

Reference: Controlling EDAPRINT History

The size of the server activity log, the number of files archived in the EDAPRINT history, and the maximum number of days each edaprint.log is maintained before it is archived and a new edaprint log is started are controlled by edaprint_max_lines, edaprint_history, and edaprint_max_days, respectively.

Limit the size of each log file by setting the maximum number of lines to a value other than zero. There is no minimum, but the recommended value is at least 1000 lines. If the limit is too low and the system is too fast (such that two archived files can have the same file system time stamp to the same second), whichever of the archived files is deleted first is undefined.

The first log file for each server start always contains more lines than the maximum because the count begins only after the edaplog process is created, thus it is larger by the size of the startup information. Each time the limit is reached, the current log file is archived and the new file starts with an additional identification line. This line indicates the rank of the file in the series of continuation files, and a reference to the archived name of the first file in the series (the one with the startup information), in a format similar to the following:

continuation #n of edapriNN

The number of files kept archived is determined by setting the edaprint_history parameter to the maximum number of edapriNN.log files. Each time the server is restarted or the current log reaches maximum size, the previous edaprint file is moved to edapriNN.log, and the maximum number of files is enforced by deleting the oldest files. The effective minimum number of files kept may be as high as 2 in addition to the current edaprint.log, even if edaprint_history was set to 0 or 1 because when files are split to respect edaprint_max_lines, the most recent file and the most recent file containing startup information are always preserved.