Cisco Cisco Unified Customer Voice Portal 10.5(1) User Guide
C
HAPTER
5:
V
OICE
XML
S
ERVER
L
OGGING
V
OICE
XML
S
ERVER
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
76
No logging cache is used, meaning that when a logging event occurs in a call, it is placed into
the activity log immediately. This allows for real-time logging but incurs a performance
overhead in managing much more IO operations.
overhead in managing much more IO operations.
No file purging will take place. The administrator is responsible for maintaining the logs on
the system.
The Application Error Log
During the voice application development process, errors can be introduced by configuring
elements incorrectly, spelling mistakes in audio filenames, or by Java coding bugs. In each of
these cases errors occur while running the application. While the Activity Logger does report
errors, it is preferable to isolate errors in a separate file so that they are easily found and dealt
with. Additionally, when reporting Java errors, a stack trace is desired. The application Error
Logger provides a place for these errors to appear. The error log file names are in the form
“error_logYYYY-MM-DD.txt” where YYYY, MM, and DD are the year, month, and day when
the error log was first created and is rotated daily.
elements incorrectly, spelling mistakes in audio filenames, or by Java coding bugs. In each of
these cases errors occur while running the application. While the Activity Logger does report
errors, it is preferable to isolate errors in a separate file so that they are easily found and dealt
with. Additionally, when reporting Java errors, a stack trace is desired. The application Error
Logger provides a place for these errors to appear. The error log file names are in the form
“error_logYYYY-MM-DD.txt” where YYYY, MM, and DD are the year, month, and day when
the error log was first created and is rotated daily.
Note that the Error Logger will report information on errors that are affiliated with the
application in which it is configured. It can even report errors encountered by other loggers in the
same application only if the Error Logger is listed before other loggers in the application. If
another logger is loaded before the Error Logger, any errors it encounters will be logged instead
to the VoiceXML Server Call Error Log. It is for this reason that by default Unified CVP
VoiceXML Studio puts the Error Logger at the top of the list of loggers to use for a new
application.
application in which it is configured. It can even report errors encountered by other loggers in the
same application only if the Error Logger is listed before other loggers in the application. If
another logger is loaded before the Error Logger, any errors it encounters will be logged instead
to the VoiceXML Server Call Error Log. It is for this reason that by default Unified CVP
VoiceXML Studio puts the Error Logger at the top of the list of loggers to use for a new
application.
The columns of the error log are:
SessionID
. The session ID of the application visit described in the VoiceXML Server Call
Log section.
Time
. The time the error occurred.
Description
. The error description including a Java stack trace if applicable.
The Error Logger utilizes a configuration to control two different aspects of the error logs: the
format of the files and how often should log files be purged. This configuration is specified as an
XML file created by the designer in Unified CVP VoiceXML Studio.
format of the files and how often should log files be purged. This configuration is specified as an
XML file created by the designer in Unified CVP VoiceXML Studio.