Changing the log level during a run

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.

About this task

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. However, under certain conditions, you yourself 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.


To change the log level during a run:
  1. From the test editor, click Run Test. The execution report launches either in the internal or external browser, and the state of the run is shown as Running.
  2. During the run, click Running > Change Log Level.
  3. To change the log level, select any of the following options:
    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 require corrective action.
    None Turns logging off.
  4. Click Change.


When a user group runs on your local computer, the problem determination logs are in the deployment_root directory in your 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.
Note: 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 that of the problem run. The most recent log has the suffix 00.log.