Cisco Cisco Unified Contact Center Enterprise 9.0(1)
Serviceability Best Practices Guide for Unified ICM/Unified CCE & Unified CCH
©2012 Cisco Systems, Inc.
205
10.5 DUMPLOG
Using the DUMPLOG Utility Optional Cisco Log Message Format
The DUMPLOG utility converts binary log files written by Unified ICM/Unified CCE processes into
readable text format. An enhancement was added to DUMPLOG with Release 7.2(1) of the Unified
ICM/Unified CCE to optionally display the binary log files in Cisco Log message format. For more
information about the Cisco Log format, see section 5.1. For more information about this utility, see
the How to Use the DumpLog Utility Tech Note in
readable text format. An enhancement was added to DUMPLOG with Release 7.2(1) of the Unified
ICM/Unified CCE to optionally display the binary log files in Cisco Log message format. For more
information about the Cisco Log format, see section 5.1. For more information about this utility, see
the How to Use the DumpLog Utility Tech Note in
Header
Cisco Log formatted log entries include a more comprehensive header compared to DUMPLOG
standard format.
standard format.
DumpLog Standard Format
Standard formatted DUMPLOG entries display the following fields:
<TIMESTAMP> <COMPONENT-PROCESS> <MESSAGE>
The timestamp is represented as a 24-hour value (hh:mm:ss). It does not include the date, which
appears on a separate line at the beginning of the file and when a new day starts. For example:
appears on a separate line at the beginning of the file and when a new day starts. For example:
Events from February 8, 2007
00:37:44 ra-rtr MDS is in service.
00:37:44 ra-rtr MDS is in service.
Cisco Log Format
Cisco Log formatted DUMPLOG entries display the following fields:
<SEQNUM>: <HOST>: <TIMESTAMP> <TIMEZONE>: %APPNAME: %<TAGS>:<MESSAGE>
Below is an example of a Cisco Log formatted DUMPLOG message. An actual log entry appears on
a single line.
a single line.
10: CICMRGRA: Feb 8 2007 05:37:44.658 +0000: %ICM_Router_ProcessSynchronization: [comp=Router-
A][pname=rtr][iid=ipcc][sev=info]: MDS is in service.
A][pname=rtr][iid=ipcc][sev=info]: MDS is in service.
Note: The contents of the APPNAME and TAGS fields differ from those previously described in section 5.1.
Table 10-12: APPNAME and TAGS Used in DUMPLOG Trace Output
Field
Description
APPNAME
PRODUCT_COMPONENT_MESSAGECATEGORY
PRODUCT - always ICM
COMPONENT – such as Router
MESSAGECATEGORY – such as ProcessSynchronization
TAGS
Acceptable tags are:
[comp=%s] - component name including side, such as Router A
[pname=%s] - process name, such as rtr