Cisco Cisco Customer Voice Portal Downloads Mode D'Emploi
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
105
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.
The
<scope>
tag defines the logging level to use in the
logging_level
attribute. The child tag
<definitions>
encapsulates all possible logging levels. All Activity Logger configurations are
required to define a scope with at least one logging level.
To define a logging level, a separate
<level>
tag is added within the
<definitions>
tag and
given a name in the
name
attribute. This tag will include a separate
<event>
tag for each event
the logging level includes. The
id
attribute defines the name of the event. Table 5-2 lists all
possible event IDs and describes when that event occurs.
Note that at minimum, the start and end events are required for any logging level as these events
are used by the Activity Logger to maintain information about its log files and which calls are
using them.
are used by the Activity Logger to maintain information about its log files and which calls are
using them.