Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
5:
C
ALL
S
ERVICES
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
114
to
milliseconds
, the number will be 13 digits in length (representing the number of
milliseconds elapsed since that date).
•
print_stack_traces
. This required attribute is set to either
true
or
false
and determines
whether the error log will contain Java stack traces. Stack traces are very useful to a
developer in tracking down the cause of a Java error so it is recommended to keep this option
on.
developer in tracking down the cause of a Java error so it is recommended to keep this option
on.
Error Logger Configuration: File Purging
The Error Logger can be configured to automatically delete files that conform to certain criteria.
Properly configured, this will allow an administrator to avoid having the system’s hard drive fill
up with logs, which would prevent new calls from being logged.
Properly configured, this will allow an administrator to avoid having the system’s hard drive fill
up with logs, which would prevent new calls from being logged.
A few notes about file purging must be given:
• Since loggers are activated only when events occur in a call, the file purging activity will
only take place when an error event occurs. As a result, a system that encounters no errors
will not automatically delete files until a new error occurs.
will not automatically delete files until a new error occurs.
• When the Error Logger starts up for the first time, it will apply the purging strategy on any
files that exist in the logger directory. Therefore, if an application server is shut down with
files in the logger directory and then restarted a long time later, these files could be deleted
when the application server starts up and the logger initializes.
files in the logger directory and then restarted a long time later, these files could be deleted
when the application server starts up and the logger initializes.
• Unlike the Activity Logger, the Error Logger applies its purging strategy to any files found in
its logger directory, including non-error log files. So should other files be added to the logger
folder after the application server has started could be deleted when the Error Logger
encounters a new error.
folder after the application server has started could be deleted when the Error Logger
encounters a new error.
The optional
<purge>
tag defines the purging strategy. If this tag does not appear in the
configuration, no file purging will take place. The tag can contain one of the following child
tags:
tags:
•
file_age
. The Error Logger will delete error log files older than X days, where X is an integer
greater than 0 specified in the
older_than
attribute.
•
file_count
. The Error Logger will delete error log files if the logger folder contains greater
than X files, where X is an integer greater than 0 specified in the
greater_than
attribute.
When the files are deleted, the oldest ones are deleted first until the folder reaches the desired
file count.
file count.
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">