Cisco Cisco Unified Customer Voice Portal 10.5(1) 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) 

 

 

 

 

 

75

    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. 

    The cache is set to 10K or 5000 characters and is allocated once at the start of a call. 

    Files that are older than 3 days that appear in the logger instance’s dedicated directory will be 

purged. 

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE configuration SYSTEM "../../../../dtds/ActivityLoggerConfig.dtd"> 
<configuration version="1.0" name="MyLogger2"> 
 

<format delimiter="," remove_delimiter_from_content="false" 

date_format="minimal" date_granularity="minutes"/> 
 <scope 

logging_level="MyLoggingLevel"> 

  <definitions> 
   <level 

name="MyLoggingLevel"> 

    <event 

id="start"/> 

    <event 

id="end"/> 

    <event 

id="elementEnter"/> 

    <event 

id="elementFlag"/> 

    

    <event 

id="elementExit"/> 

   </level> 
  </definitions> 
 </scope> 
 <rotation> 
  <by_size 

mb_limit="100"/> 

 </rotation> 
</configuration> 

This configuration has the following features: 

    The activity logs will be delimited with a comma and will not remove any commas that 

appear in the content potentially complicating any importing of these logs into spreadsheets 
or databases. 

    The activity logs will end each line with the character appropriate for the operating system on 

which it is generated. So if this system is running under Windows, the activity logs will look 
fine under Notepad and if this system is running under Unix, the activity logs will use the 
Unix end of line characters that would not be recognized if opened by Windows Notepad. 

    Dates in the activity logs will appear in the minimal format with minute granularity. For 

example: “15:45”. 

    Only one logging level is defined that logs when calls enter and exit an application, enter and 

exit an element, and when a flag element is visited. 

    A new activity log is created when the previous one has reached approximately 100MB in 

size, regardless on whether the calls spanned weeks or hours.