Cisco Cisco Unified Customer Voice Portal 11.0(1) Guida Utente
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
110
Activity Logger Configuration Example #1
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE configuration SYSTEM "../../../../dtds/ActivityLoggerConfig.dtd">
<configuration version="1.0" name="MyLogger1">
<!DOCTYPE configuration SYSTEM "../../../../dtds/ActivityLoggerConfig.dtd">
<configuration version="1.0" name="MyLogger1">
<format delimiter="\t" remove_delimiter_from_content="true"
end_of_line="\n" date_format="standard" date_granularity="milliseconds"/>
<scope
<scope
logging_level="Complete">
<definitions>
<level
<level
name="Minimal">
<event
id="start"/>
<event
id="end"/>
</level>
<level
<level
name="Complete">
<event
id="start"/>
<event
id="end"/>
<event
id="elementEnter"/>
<event
id="elementExit"/>
<event
id="elementFlag"/>
<event
id="defaultInteraction"/>
<event
id="elementData"/>
<event
id="custom"/>
<event
id="hotlink"/>
<event
id="hotevent"/>
<event
id="warning"/>
</level>
</definitions>
</scope>
<rotation>
<by_day
</definitions>
</scope>
<rotation>
<by_day
every="2"/>
</rotation>
<cache>
<per_call
<cache>
<per_call
kb_limit="10"
allocate="once"/>
</cache>
<purge>
<file_age
<purge>
<file_age
older_than="3"/>
</purge>
</configuration>
</configuration>
This configuration has the following features:
•
The activity logs will be delimited with a tab (“\t”) and will have any tabs that appear in the
content removed.
content removed.
•
The activity logs will use a Unix-style new line character (“\n”) to delimit lines. As a result,
these log files would not appear orderly on Windows Notepad because it does not recognize
these new line characters.
these log files would not appear orderly on Windows Notepad because it does not recognize
these new line characters.
•
Dates in the activity logs will appear in the standard format with millisecond granularity. For
example: “05/09/2006 15:45:02.654”
example: “05/09/2006 15:45:02.654”
•
Two logging levels are defined: Minimal, which logs only when a caller entered and exited
an application, and Complete, which logs all events. The Complete logging level is the one
that will be used.
an application, and Complete, which logs all events. The Complete logging level is the one
that will be used.
•
The activity log files will be rotated every two days, meaning each log file will contain 2
days worth of calls before a new file is created.
days worth of calls before a new file is created.