Cisco Cisco Unified Customer Voice Portal 10.5(1) Note De Mise
C
HAPTER
5:
VXML Server
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
115
Error Logger Configuration Example #1
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE configuration SYSTEM
"../../../../dtds/ApplicationErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyErrorLogger1">
<!DOCTYPE configuration SYSTEM
"../../../../dtds/ApplicationErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyErrorLogger1">
<format delimiter="," remove_delimiter_from_content="true"
date_format="standard" date_granularity="seconds" print_stack_traces="true"/>
<purge>
<file_count
<purge>
<file_count
greater_than="10"/>
</purge>
</configuration>
</configuration>
This configuration has the following features:
•
The error logs will be delimited with a comma and will have any commas that appear in the
content removed.
content removed.
•
Dates in the error logs will appear in the standard format with seconds granularity. For
example: “05/09/2006 15:45:02”
example: “05/09/2006 15:45:02”
•
Java stack traces will appear in the error logs. Note that since stack traces span multiple lines,
including stack traces may complicate the process of importing the error logs into
spreadsheets or databases. This is rarely done for error logs anyway.
including stack traces may complicate the process of importing the error logs into
spreadsheets or databases. This is rarely done for error logs anyway.
•
When a new file is added to logger instance’s dedicated directory by the Error Logger, if the
directory contains more than 10 files the oldest file will be deleted.
directory contains more than 10 files the oldest file will be deleted.
Error Logger Configuration Example #2
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE configuration SYSTEM
"../../../../dtds/ApplicationErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyErrorLogger2">
<!DOCTYPE configuration SYSTEM
"../../../../dtds/ApplicationErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyErrorLogger2">
<format delimiter="***" remove_delimiter_from_content="false"
date_format="minimal" date_granularity="seconds" print_stack_traces="false"/>
</configuration>
</configuration>
This configuration has the following features:
•
The error logs will be delimited with the string “***” and will not attempt to remove that
string from the content. Note that the delimiter does not need to be limited to a single
character and can be a multi-character string. Usually, though, it is a single character to make
importing into spreadsheets and databases straightforward.
string from the content. Note that the delimiter does not need to be limited to a single
character and can be a multi-character string. Usually, though, it is a single character to make
importing into spreadsheets and databases straightforward.
•
Dates in the error logs will appear in the minimal format with seconds granularity. For
example: “15:45:02”
example: “15:45:02”
•
Java stack traces will not appear in the error logs. When a Java exception occurs, only the
error message itself will appear in the error log without the stack trace.
error message itself will appear in the error log without the stack trace.
•
No file purging will take place. The administrator is responsible for maintaining the logs on
the system.
the system.