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\rptUser\A1E14699848784C00D2DEB73763646462\CommonBaseEvents00.log. If a large amount of log information is generated, multiple CommonBaseEvents files are created.
To set the level of problem-determination logging and the sampling rate:
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. |
Option | Description |
---|---|
Fixed number of users | The number is applied to each user group. Assume that your schedule contains two user groups. One group contains four users, and one group contains 1000 users. If you specify 2 for this option, two users are sampled from each group. |
Percentage of users | The percentage is applied to each user group—but at least one user will be sampled from each group. Assume that your schedule contains two user groups. One group contains four users, and one group contains 1000 users. If your sampling rate is 10%, one user is sampled from the first group, and 100 users are sampled from the second group. If your sampling rate is 25%, one user is sampled from the first group, and 250 users are sampled from the second group. |
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.