Set the log level during a run

Overview

You can change the log level to determine problems during a run. By default, only warnings and severe errors are logged. Typically, you change this level only when requested to do so by IBM Software Support.

Although the test log provides general information about problems that occur during a run, you might need to investigate certain problems further by examining a detailed trace of the run. In general, change the problem determination level only when asked to by technical support.

Under certain conditions, you might want to change the problem determination level. For example, if problems occur when a run reaches a certain number of users, you might increase the level to Config, which is the most detailed level that you will generally use

Change the log level during a run

1. Start the run and in the Performance Test Runs view, click the Change Log Level icon.

2. To change the log level, select any of the following options:

   Option	Description
   All, Finest, Finer, Fine	Set these options only if you are requested to do so by technical support.
   Config	Logs static configuration messages. Configuration messages, which include hardware specifications or system profiles, require no corrective action.
   Info	Logs informational messages. Informational messages, which include system state, require no corrective action.
   Warning	Logs warning messages. This is the default setting. Warning messages, which might indicate potential problems, require no corrective action.
   Severe	Logs critical and unrecoverable errors. Critical and unrecoverable messages interrupt normal program execution, and you need to take corrective action.
   None	Turns logging off.

3. Click Finish.

Results

When a user group runs on your local computer, the problem determination logs are in the deployment_root directory in the workspace. When a user group runs at a remote location, which is the typical use case, each remote location has a deployment directory, which you define and which is listed on the Locations page for that user group.

Common Base Event XML logs from remote locations use Universal Coordinated Time (UTC), also called Zulu time, which is likely different from your local time. For example, eastern standard time (EST) is 5 hours behind UTC time.

What to do next

To view the problem determination log, open the log file in an XML editor. Select the log whose timestamp matches the problem run. The most recent log has the suffix 00.log.

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.