If you need detailed trace logs for the workload agent
in an existing virtual application instance and
tracing of all log levels was not configured at deployment time, you
can configure detailed tracing for the workload agent in the virtual application instance.
About this task
Use these steps to configure detailed tracing for the workload
agent in the virtual application instance.Note: When
detailed tracing is enabled for the workload agent, the performance
of virtual applications might be impacted. When you no longer require
tracing to troubleshoot, reset the trace string as described at the
end of this procedure.
Procedure
- Click (or in 2.3.3.3).
- Select a virtual application instance.
- Click the Manage icon in the toolbar.
- Click the Operation tab.
- Select the Agent role from the list operations.
- Expand Update trace settings and specify the appropriate
settings:
- Trace string applied to the agent
- Type the trace string.
- The default trace string is
*=info=enabled
. This
setting records only info
level messages, which are
saved in the trace log.
- Use the following string to enable all traces. Enter the trace
string as one continuous string without spaces or line breaks.
*=info=enabled:com.ibm.maestro.common.*=all=enabled:com.ibm.maestro.agent.*=all=enabled:com.ibm.maestro.profile.
*=all=enabled:com.ibm.maestro.security.*=all=enabled:com.ibm.purescale.profile.*=all=enabled:com.ibm.purescale.security.
*=all=enabled:osgi=all=enabled:com.ibm.ws.bbson.ConfigOracle=all=enabled:com.ibm.ws.bbson.api.connectivity.local.
*=all=enabled:com.ibm.ws.bbson.api.traffic.local.*=all=enabled:com.ibm.ws.bbson.api.connectivity.remote.
*=all=enabled:com.ibm.ws.bbson.api.traffic.remote.*=all=enabled:com.ibm.ws.bbson.BBFactoryImpl
=all=enabled:com.ibm.maestro.elbservice.management.*=all=enabled:com.ibm.maestro.sharedservice.genericREST.resources.
*=all=enabled
- Trace File Name
- The name for the trace file. The default file name is trace.log.
- Trace Max File Size
- The maximum trace log file size in MB. The default size is 40
MB. When a log file reaches the specified maximum size, a new log
file is created. The file name for the new trace log includes a numeric
suffix, and the suffix increments for each new file. For example, trace.log.1, trace.log.2, trace.log.3.
- Trace Max File Number
- The maximum number of trace log files that can be created. The
default is 20 files. Each trace log file has a numeric suffix. For
example, trace.log.0, trace.log.1, trace.log.2, trace.log.3.
If the maximum number of files is reached, a new sequentially numbered
trace log file is created and the oldest trace log file is deleted.
For example, if the maximum value is 20, only 20 trace log files are
saved at a time. The file trace.log.20 is created
when trace.log.19 reaches the maximum file size
and trace.log.0 is deleted.
- Append to trace file
- If this option is selected, data is appended to the most recent
existing trace log file each time a new set of information is recorded
to the trace log until the maximum file size is reached. If this option
is not selected, a new trace log file is created each time a new set
of information is required in the trace log, even if the maximum file
size of the most recent log file is not reached.
- Click Submit.
Tracing is configured for all the
workload agents in the deployment.
- To view the trace logs for the agent, complete the following steps:
- Click the Logging tab.
Logs are organized by virtual machine name, and each name contains the name of the
roles that are associated with the virtual machine. A role within a virtual application
refers to the software that is installed and configured.
- Expand the IWD Agent role and then expand the
entry with the /logs subdirectory.
For example, if the virtual machine name is
Web_Application-was.11332975226124
, expand the entry
Web_Application-was.11332975226124/logs
.
The log file with the file name that you
configured is listed under the /logs directory. Select the trace log to view
the contents in the detail pane.
- When you no longer need the trace logs for troubleshooting or debugging, reset the trace
string.
Repeat the preceding steps and set the trace string as in the following
example:
*=info=enabled