Cisco Cisco Customer Voice Portal Downloads Release Note
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
96
•
<http_headers>
. This optional tag is used to indicate that an error caused by an unrecognized
URL (such as a request for an application that does not exist) should include the HTTP
headers passed to the URL. This can be helpful to know since it could help determine why the
request was made. The
headers passed to the URL. This can be helpful to know since it could help determine why the
request was made. The
length
attribute provides a limit, in a number of characters, to be
included in the log. This prevents the log from being filled up with too much header data.
Note that the header data appears on one line, no matter how long.
Note that the header data appears on one line, no matter how long.
Global Error Logger Configuration: File Purging
The Global 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.
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.
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.
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.
•
When the Global 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.
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.
•
The Global 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.
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.
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 Global 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 Global 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.
the desired file count.
Global Error Logger Configuration Example #1
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE configuration SYSTEM "../dtds/GlobalErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyGlobalErrorLogger1">
<log_details>
<stacktraces/>
<http_parameters
<!DOCTYPE configuration SYSTEM "../dtds/GlobalErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyGlobalErrorLogger1">
<log_details>
<stacktraces/>
<http_parameters
length="100"/>
<http_headers
length="300"/>