Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
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
93
Call Services communicates with loggers by triggering logging events that the loggers listen for
and then deal with. Call Services activates loggers in a fully multi-threaded environment to
maximize performance.
and then deal with. Call Services activates loggers in a fully multi-threaded environment to
maximize performance.
Loggers are divided into two categories: global loggers and application loggers. Global loggers
are activated by logging events that apply to Call Services as a whole and that is not directly
related to any particular application (for example a record of all calls made to the Call Services
instance). Application loggers are activated by logging events that apply to a particular
application running on Call Services (for example a call visiting an element). Each logger type
deals with a separate list of possible logging events and a different Java API is used. Each logger
type is also given a separate area to store logs, though a logger may choose to ignore this area in
the case that it does not log to files.
are activated by logging events that apply to Call Services as a whole and that is not directly
related to any particular application (for example a record of all calls made to the Call Services
instance). Application loggers are activated by logging events that apply to a particular
application running on Call Services (for example a call visiting an element). Each logger type
deals with a separate list of possible logging events and a different Java API is used. Each logger
type is also given a separate area to store logs, though a logger may choose to ignore this area in
the case that it does not log to files.
Global Loggers
The
global_config.xml
file found in the
conf
directory of Audium Home is used to define the
global loggers Call Services is to use. The administrator can define any number of global loggers
to be simultaneously active, even multiple instances of the same logger class. This file also lists
the names of the configuration files for these loggers, if they are configurable. The configuration
files must be placed in the same
to be simultaneously active, even multiple instances of the same logger class. This file also lists
the names of the configuration files for these loggers, if they are configurable. The configuration
files must be placed in the same
conf
directory as the
global_config.xml
file. The
global_config.xml
file and any configuration files must be edited by hand, there is no
interface for editing them. Refer to Chapter 6: Call Services Configuration for more details about
this file and how to define global loggers within it.
this file and how to define global loggers within it.
Global loggers will be loaded by Call Services when it starts up and remain in memory until it is
shut down. Any change made to the
shut down. Any change made to the
global_config.xml
file will not be loaded until Call
Services is restarted.
Call Services provides the
logs
folder of Audium Home for log file storage should the Global
Loggers require it. To keep each logger instance’s logs separate, a subfolder with the name of
the logger instance is created and all logs generated by the logger instance are stored there.
the logger instance is created and all logs generated by the logger instance are stored there.
By default, Call Services utilizes three loggers to create text log files containing Call Services-
specific information: a log that keeps track of calls made to the system, a log for tracking Call
Services administration activity, and an log that shows errors that occur on the Call Services
level (as opposed to the application level). The global error logger requires a configuration that
allows for detailed control over how the logger operates.
specific information: a log that keeps track of calls made to the system, a log for tracking Call
Services administration activity, and an log that shows errors that occur on the Call Services
level (as opposed to the application level). The global error logger requires a configuration that
allows for detailed control over how the logger operates.
The following sections describe these three pre-built global loggers, their configurations (if any),
and the information stored in their logs.
and the information stored in their logs.
The Global Call Logger
The global call logger records a single line for every application visit handled by Call Services
into a text call log. Most calls will begin and end in a single application so in that case a line in
into a text call log. Most calls will begin and end in a single application so in that case a line in