Cisco Cisco Customer Voice Portal Downloads 릴리스 노트
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
98
Error Logger Configuration Example #2
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE configuration SYSTEM "../dtds/GlobalErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyGlobalErrorLogger2">
<log_details>
<on_hold_calls
<!DOCTYPE configuration SYSTEM "../dtds/GlobalErrorLoggerConfig.dtd">
<configuration version="1.0" name="MyGlobalErrorLogger2">
<log_details>
<on_hold_calls
application_name="true"/>
</log_details>
<purge>
<file_count
<purge>
<file_count
greater_than="100"/>
</purge>
</configuration>
</configuration>
This configuration has the following features:
•
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.
•
When a call is put on hold, that fact will be logged along with the application name that the
caller was attempting to visit.
caller was attempting to visit.
•
If there is a bad URL error message, only the URL itself will be logged without any HTTP
parameters or headers.
parameters or headers.
•
No file purging will take place. The administrator is responsible for maintaining the logs on
the system.
the system.
The Global Administration History Logger
The Global Administration History Logger records administration events that occur on VXML
Server itself. Application-level administration history is logged by application-level loggers,
which are described later in this chapter. These events are triggered by an administrator
executing administration script (see Chapter 3: Administration for more on administering VXML
Server).
Server itself. Application-level administration history is logged by application-level loggers,
which are described later in this chapter. These events are triggered by an administrator
executing administration script (see Chapter 3: Administration for more on administering VXML
Server).
The administration log file names begin with “admin_historyYYYY-MM-DD.txt” where
YYYY, MM, and DD are the year, month, and day when the administration log was first created.
By default, the log folder for is named “GlobalAdminLogger” (though the name is set in the
YYYY, MM, and DD are the year, month, and day when the administration log was first created.
By default, the log folder for is named “GlobalAdminLogger” (though the name is set in the
global_config.xml
file and can be changed by the administrator). Administration history log
files are rotated daily. Note that if no administration activity occurred on a particular day, no
administration history log will be created.
administration history log will be created.
The file contains three columns: the time, what script was run, and its result, separated by
commas. The result is usually “success” and if not, contains the description of the error
encountered. The possible values of the result are:
commas. The result is usually “success” and if not, contains the description of the error
encountered. The possible values of the result are: