Setting problem determination level for tests

You can set the level of information that is saved in the problem determination log during a run. By default, only warnings and severe errors are logged. Typically, you change this log level only when requested to do so by the Support person.

About this task

The problem determination logs contain internal information about the playback engine. These logs are particularly useful for debugging problems such as Kerberos authentication, SSL negotiation, and resource constraints on an agent. The log files are named CommonBaseEvents00.log and are located in the deployment directory. For example, if you play back a schedule on an agent and set C:\Agent as the deployment directory, the problem determination log files are in a directory similar to C:\Agent\deployment_root\<UserName>\A1E14699848784C00D2DEB73763646462\CommonBaseEvents00.log. If a large amount of log information is generated, multiple CommonBaseEvents files are created.


  1. Open the test for which you want to set the problem determination log level.
  2. Select the root node and from the Test Details section, select Problem Determination.
  3. On the Problem Determination page, set Problem determination log level to one 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. Save the test.