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
113
Error Logger Configuration: Format
The
<format>
tag allows for the modification of how the error log files are formatted. All Error
Logger configurations are required to define a format. The possible attributes are:
•
delimiter
. This required attribute defines the delimiter to use to separate columns on a line.
Delimiters can be any string value, though typically will be a comma or tab. To use a special
white space character such as a new line or tab, use the escaped version. The possible values
are “\n” (denoting a new line), “\t” (denoting a tab), “\r” (denoting a return), and “\f”
(denoting a line feed).
white space character such as a new line or tab, use the escaped version. The possible values
are “\n” (denoting a new line), “\t” (denoting a tab), “\r” (denoting a return), and “\f”
(denoting a line feed).
•
remove_delimiter_from_content
. When this required attribute is set to
true
, the Error Logger
will attempt to eliminate the delimiter from any content appearing in the logs to ensure that
the log file can be imported flawlessly. For example, if the delimiter is a comma and the
configuration is set to remove the delimiter, when it is to log the content “This, is the
description”, it will appear in the log as “This is the description” so as not to affect the
accuracy of the importing process. This extra step, though, does incur a slight performance
hit. This step will not be performed if this attribute is set to
the log file can be imported flawlessly. For example, if the delimiter is a comma and the
configuration is set to remove the delimiter, when it is to log the content “This, is the
description”, it will appear in the log as “This is the description” so as not to affect the
accuracy of the importing process. This extra step, though, does incur a slight performance
hit. This step will not be performed if this attribute is set to
false
. Note that should the error
log contain Java stack traces, the error logs could be difficult to import as stack traces fill
multiple lines (though their content will be cleaned of the delimiter if desired).
multiple lines (though their content will be cleaned of the delimiter if desired).
•
date_format and date_granularity
. These required attributes set how the second column of the
error log references a date when the event occurred. The format and granularity are specified.
There are three possible values for the
There are three possible values for the
date_format
attribute:
o
standard
. This is a standard readable date format in the form “MM/DD/YYYY
HH:MM[:SS][.MMM]” where the hour is in 24-hour time and the last three digits are the
milliseconds. The seconds and milliseconds are displayed with brackets to indicate that
their appearance are based on the
milliseconds. The seconds and milliseconds are displayed with brackets to indicate that
their appearance are based on the
date_granularity
attribute. For a
date_granularity
attribute set to
minutes
, just the hours and minutes of the time will be displayed. For a
granularity set to
seconds
, just the hours, minutes and seconds will be displayed. For a
granularity set to
milliseconds
, all components will be displayed.
o
minimal
. This is a minimal time value that omits the date and is in the form
“HH:MM[:SS][.MMM]” where the hour is in 24-hour time and the last three digits are
the milliseconds. The seconds and milliseconds are displayed with brackets to indicate
that their appearance are based on the
the milliseconds. The seconds and milliseconds are displayed with brackets to indicate
that their appearance are based on the
date_granularity
attribute. For a
date_granularity
attribute set to
minutes
, just the hours and minutes will be
displayed. For a granularity set to
seconds
, just the hours, minutes and seconds will be
displayed. For a granularity set to
milliseconds
, all components will be displayed.
o
number
. This displays a large integer number representing the full date and time as an
elapsed time since January 1, 1970, 00:00:00 GMT. For a
date_granularity
attribute
set to
minutes
, the number will be 8 digits in length (representing the number of minutes
elapsed since that date). For a granularity set to
seconds
, the number will be 10 digits in
length (representing the number of seconds elapsed since that date). For a granularity set