Cisco Cisco Customer Voice Portal Downloads User Guide
C
HAPTER
5:
V
OICE
XML
S
ERVER
L
OGGING
V
OICE
XML
S
ERVER
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
69
end_of_line
. This optional attribute controls the delimiter used to separate lines. The
recommended option is to not include the attribute. In this case, the Activity Logger will
separate lines appropriate to the operating system on which Unified CVP VoiceXML Server
is running. Set the attribute to explicitly set the new line delimiter. Delimiters can be any
string value, though typically will be a white space character. 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).
separate lines appropriate to the operating system on which Unified CVP VoiceXML Server
is running. Set the attribute to explicitly set the new line delimiter. Delimiters can be any
string value, though typically will be a white space character. 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).
date_format and date_granularity
. These required attributes set how the second column of the
activity log references a date when the event occurred. The format and granularity are
specified. There are three possible values for the
specified. 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
to
to
milliseconds
, the number will be 13 digits in length (representing the number of
milliseconds elapsed since that date).
Activity Logger Configuration: Scope
The Activity Logger configuration provides the administrator the ability to control what is
logged based on their own needs. This is done by defining logging levels and the events that each
level contains. During the debugging stage, for example, the logging level can be set to record all
events and once in production, the logging level can be set to record more important events.
logged based on their own needs. This is done by defining logging levels and the events that each
level contains. During the debugging stage, for example, the logging level can be set to record all
events and once in production, the logging level can be set to record more important events.