Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
5:
C
ALL
S
ERVICES
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
C
ALL
S
ERVICES
,
U
NIVERSAL
E
DITION
AND
U
NIFIED
C
ALL
S
TUDIO
107
Activity Logger Configuration: File Rotation
In any system that stores information in log files, high volume can make these files get very
large. The desire is to have a strategy for creating new log files in order to avoid files that are too
large. Additionally, file rotation strategies can help separate the log files into more logical parts.
The Activity Logger defines several rotation strategies to choose from. Note that in order to
ensure that the information for a single call is not split across multiple log files, the Activity
Logger ensures that all call information appears in the log that was active when the call was
received. As a result, it is possible for calls to be updating both pre and post rotation log files
simultaneously. Each rotation strategy determines how the log files are named (though all
activity log filenames begin with “activity_log”).
large. The desire is to have a strategy for creating new log files in order to avoid files that are too
large. Additionally, file rotation strategies can help separate the log files into more logical parts.
The Activity Logger defines several rotation strategies to choose from. Note that in order to
ensure that the information for a single call is not split across multiple log files, the Activity
Logger ensures that all call information appears in the log that was active when the call was
received. As a result, it is possible for calls to be updating both pre and post rotation log files
simultaneously. Each rotation strategy determines how the log files are named (though all
activity log filenames begin with “activity_log”).
The
<rotation>
tag defines the rotation strategy to use by containing one of the following tags:
•
<by_day>
. This strategy will create a new log file every X days where X is an integer value
greater than 0 specified in the
every
attribute. Typically this value is 1, meaning that every
day at midnight, a new log file is created. For low volume systems, the value can be given a
larger value. For example, when set to 7, a new log file is created once a week. The log files
are named “activity_logYYYY-MM-DD.txt” where YYYY is the year, MM is the month,
and DD is the day that the file is created.
larger value. For example, when set to 7, a new log file is created once a week. The log files
are named “activity_logYYYY-MM-DD.txt” where YYYY is the year, MM is the month,
and DD is the day that the file is created.
•
<by_hour>
. This strategy will create a new log file every X hours where X is an integer value
greater than 0 specified in the
every
attribute. There is no upper bound on this value, so it
can be greater than 24. The log files are named “activity_logYYYY-MM-DD-HH.txt” where
YYYY is the year, MM is the month, DD is the day, and HH is the hour that the file is
created. Note that the hour is measured in 24-hour time (0 - 23).
YYYY is the year, MM is the month, DD is the day, and HH is the hour that the file is
created. Note that the hour is measured in 24-hour time (0 - 23).
•
<by_call>
. This strategy will create a separate log file for each call made to the application.
The log files are named “activity_logYYYY-MM-DD-HH-SESSIONID.txt” where YYYY is
the year, MM is the month, DD is the day, and HH is the hour that the file is created (in 24-
hour time) and SESSIONID is the Call Services session ID (e.g. “activity_log2000-01-01-17-
192.168.1.100.1024931901079.1.MyApp.txt”). The session ID is included in the filename to
ensure uniqueness of the files. Note that care must be taken before using this log file rotation
strategy on systems with high load as this will create a very large number of files.
the year, MM is the month, DD is the day, and HH is the hour that the file is created (in 24-
hour time) and SESSIONID is the Call Services session ID (e.g. “activity_log2000-01-01-17-
192.168.1.100.1024931901079.1.MyApp.txt”). The session ID is included in the filename to
ensure uniqueness of the files. Note that care must be taken before using this log file rotation
strategy on systems with high load as this will create a very large number of files.
•
<by_size>
. This strategy will create a separate log file once the previous log file has reached
X megabytes in size where X is an integer value greater than 0 specified in the
mb_limit
attribute. Note that due to the fact that multiple calls will be updating the same file and that
the Activity Logger will ensure that all data for a single call appear in the same log file, the
final log file may be slightly larger than the limit. The log files are named
“activity_logYYYY-MM-DD-HH-MM-SS.txt” where YYYY is the year, the first MM is the
month, DD is the day, HH is the hour (in 24-hour time), the second MM is the minute, and
SS is the second that the file is created. The time information is included in the file name in
order to ensure uniqueness.
the Activity Logger will ensure that all data for a single call appear in the same log file, the
final log file may be slightly larger than the limit. The log files are named
“activity_logYYYY-MM-DD-HH-MM-SS.txt” where YYYY is the year, the first MM is the
month, DD is the day, HH is the hour (in 24-hour time), the second MM is the minute, and
SS is the second that the file is created. The time information is included in the file name in
order to ensure uniqueness.