Cisco Cisco Customer Response Solution Downloads Troubleshooting Guide
4-3
Cisco Unified Contact Center Express Servicing and Troubleshooting Guide, Release 7.0(1)
Chapter 4 Trace
Trace Level Options
•
Number of Trace Files—Enter the number of trace files that the system will create before starting
to overwrite existing files. The system will create a new trace file each time the existing one reaches
the size specified in the Trace File Size field. The default number of trace files is 10.
to overwrite existing files. The system will create a new trace file each time the existing one reaches
the size specified in the Trace File Size field. The default number of trace files is 10.
•
Trace File Size—You can configure the file size, or you can enter the maximum size, in bytes, of
the trace file. The default files size is 1048576.
the trace file. The default files size is 1048576.
Step 4
Click Update.
Trace Level Options
A trace file is a log file that records activity from the Cisco Unified CCX component subsystems and
steps. Trace files let you obtain specific, detailed information about the system that can help you
troubleshoot problems.
steps. Trace files let you obtain specific, detailed information about the system that can help you
troubleshoot problems.
The Cisco Unified CCX system can generate trace information for every subfacility. This information
is stored in an engine trace file. To help you control the size of an engine trace file, you specify the
subfacilities for which you want to collect information and the level of information that you want to
collect.
is stored in an engine trace file. To help you control the size of an engine trace file, you specify the
subfacilities for which you want to collect information and the level of information that you want to
collect.
The Cisco Unified CCX system also generates information about all threads that are running on the
system. This information is stored in the thread dump trace file and is useful for troubleshooting.
system. This information is stored in the thread dump trace file and is useful for troubleshooting.
A trace file that records all information for a component, such as the Cisco Unified CCX Engine, can
become large and difficult to read. To help you manage the trace file, the Cisco Unified CCX system lets
you specify the subfacilities for which you want to record information. These subfacilities are shown in
the following table.
become large and difficult to read. To help you manage the trace file, the Cisco Unified CCX system lets
you specify the subfacilities for which you want to record information. These subfacilities are shown in
the following table.
For each subfacility, you can select a trace level of Debugging, Alarm Tracing, both selections, or no
selections. These selections specify the messages that the system sends to a trace file.
selections. These selections specify the messages that the system sends to a trace file.
shows
the effect of each trace level settings. For an explanation of message severity levels, see
The Trace Configuration pane groups trace level options into these lists:
•
Active trace level options—Facilities and subfacilities that are running on your system
•
Inactive trace level options—Facilities and subfacilities that are not running on your system
Table 4-1
Messages Sent to a Trace File
Selection
Severity Level of
Messages Sent
Messages Sent
Explanation
Debugging
0, 1, 2, 3, 7
Sends detailed, verbose information. To be used
primarily for debugging and troubleshooting.
primarily for debugging and troubleshooting.
Alarm Tracing
0, 1, 2, 3, 4, 5, 6
Sends messages of all severity levels except
detailed debugging information.
detailed debugging information.
Debugging and Alarm
Tracing
Tracing
0, 1, 2, 3, 4, 5, 6, 7
Sends messages of all severity levels.
No selections
0, 1, 2, 3
Sends high-priority notifications, errors, and
alerts.
alerts.