You can change the level
of problem determination logging 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 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 level of problem determination
logging during a run:
Procedure
- Click
in
the Test Runs view, which displays details of the run.
- On the Problem Determination page,
set Problem determination log level to one
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. |
- Click Finish.
Results
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 is listed in the Locations page for that user
group.
Note: Common Base Event XML logs from remote locations use
UTC (also called Zulu) time, which is likely to be different from
your local time. For example, Eastern Standard Time is 5 hours behind
UTC time.
What to do next
To view the problem determination log,
click . Click , and then browse to
the appropriate Common Base Events XML log (in the deployment directory).
Select the log whose Date Modified matches
the problem run. The most recent log has the suffix 00.log.