Monitor Session Options

NOTE: This content applies to RTX64 Monitor in RTX64 4.3 and later versions. For information on RTX64 Monitor in RTX64 4.2 and earlier, see Using RTX64 Monitor (RTX64 4.2 and Earlier).

On the Session options page in RTX64 Monitor, you can:

Configure event collection
Convert session binary files into text files that show the details of events in the order in which they occurred
Delete a session file

NOTE: The changes you make to the Monitor utility settings are lost when the Subsystem is stopped.

Sections in this topic:

Configuring Event Collection
Converting Session Data to Text
Deleting Session Folders

Configuring Event Collection

Under Configure event collection, you can change the maximum number of events to collect and determine whether you would like to collect pre-start-trigger events. These settings override the default configurations in the RTX64 Control Panel.

NOTE: These settings cannot be changed when a monitoring session is running.

Setting	Description	Action
Maximum number of events to collect	Configures the maximum number of events to collect in a monitor session.	Select a radio button: Unlimited – choose this option to collect events until the monitoring session is manually stopped. This is the default option. Only collect this many events – specify a value for the maximum number of events to collect during a monitor session. The default value is 20,000 events.
Number of pre-start-trigger events to collect	Configures the number of pre-start-trigger events, if any, to collect. Pre-start-trigger events are events that occur before the event type that triggers the start of a monitoring session. NOTE: This setting requires at least one session start trigger to be set. It is grayed-out when none are set.	Specify a value for the number of pre-start-trigger events to collect during a monitor session. The default value is 0 events (no pre-start-trigger events collected). When set to a nonzero value, all monitoring events in excess of that value that occur before the start trigger happens will not be saved. NOTE: When Maximum number of events to collect is set to Only collect this many events, the number of pre-start-trigger events to collect must not exceed it.
Include network events	Determines whether network-related events, such as Network Abstraction Layer (NAL) and RT-TCP/IP Stack events, will be collected in the next monitoring session.	To include network-related events in the next monitoring session, select the Include network events check box. To exclude network-related events from event collection, clear selection of the check box.

Setting

Description

Action

Maximum number of events to collect

Configures the maximum number of events to collect in a monitor session.

Select a radio button:

Unlimited – choose this option to collect events until the monitoring session is manually stopped. This is the default option.
Only collect this many events – specify a value for the maximum number of events to collect during a monitor session. The default value is 20,000 events.

Number of pre-start-trigger events to collect

Configures the number of pre-start-trigger events, if any, to collect. Pre-start-trigger events are events that occur before the event type that triggers the start of a monitoring session.

NOTE: This setting requires at least one session start trigger to be set. It is grayed-out when none are set.

Specify a value for the number of pre-start-trigger events to collect during a monitor session. The default value is 0 events (no pre-start-trigger events collected).

When set to a nonzero value, all monitoring events in excess of that value that occur before the start trigger happens will not be saved.

NOTE: When Maximum number of events to collect is set to Only collect this many events, the number of pre-start-trigger events to collect must not exceed it.

Include network events

Determines whether network-related events, such as Network Abstraction Layer (NAL) and RT-TCP/IP Stack events, will be collected in the next monitoring session.

To include network-related events in the next monitoring session, select the Include network events check box.

To exclude network-related events from event collection, clear selection of the check box.

Converting Session Data to Text

Under Convert session data to text, you can convert monitoring data from a monitor session file (.monx) to a readable log file (.txt) and delete older sessions you no longer need.

NOTE: Converting data can take several moments if the session contains a large amount of data.

NOTE: You cannot convert a session file that is actively being updated. Attempts to do this will result in an error. To convert monitoring data from an active session, you must first stop monitoring.

To convert a session file:

In the Choose the session file to convert field, specify the monitor session file (.monx) you want to convert. Click Browse to navigate for the session file.
Specify the output text file (.txt). By default, the output file is the session folder in which the log selected for conversion resides. Click Browse to change the default location.
Click Convert File.

The text file is automatically launched in your default text editor when the conversion is completed. Each text file is 500 MB and has the form YYYYMMDD_HHMMSS_xxx.N.txt, where N is an integer from 1 to the number of 500 MB text files required to contain the information in the original binary file.

Deleting Session Folders

If you start running low on space, you can manually delete session folders to free up space.

To delete a session folder:

Choose the session folder to delete. Click Browse to navigate to the session folder you want to delete.

Subfolders use the naming convention YYYYMMDD_HHMMSS_NNN, where NNN is an integer between 000 and the total number of monitoring sessions for that second.

Click Delete Folder.