Contents

Control log verbosity

The degree of detail written to logs is determined by setting trace levels for topics in each subsystem. A subsystem typically logs messages when it passes control to a routine, encounters a problem, or otherwise needs to record work performed.

Care must be taken to use an appropriate level of verbosity, since logs can quickly grow large and add overhead to the system. The CIC utilities that manage log verbosity are CIC System Manager and Trace Configuration Utility. Each is discussed later in this document.

Trace Topics

The routines that write messages are called trace topics. Trace Topics correspond to subroutines invoked by a subsystem, or to some type of major functionality provided by an application. Every subsystem and application has its own set of trace topics.

Trace Levels

Each topic has a numeric trace level setting that controls the verbosity of messages written about that topic. Not all messages are equally important. Messages from some routines are more important than others.

Trace levels are sometimes called topic levels, since people tend to combine both terms. Topic is the subject traced and level controls to what degree the topic is traced.

Trace levels are numeric values that determine which messages are logged for a topic, based upon the severity of the message. The table below shows the range of numeric values that correspond to common trace settings. For example, a trace level in the 0-10 range would log only critical errors, while a trace setting of 100 would log every message generated by the topic.

Severity	Range	Description
Critical	0-10	Only critical errors (those impacting features) will be logged.
Error	11-20	Any error conditions will be logged.
Warning	21-40	Any warning conditions will be logged.
Status	41-60	Operations are logged.
Notes	61-80	Operations including details are logged.
Verbose	81-99	Sub-operation details are logged.
All	100	All trace statements within the program are enabled (This will generate very large log files.)

The higher the trace level, the more information will be logged. With a few exceptions, most subsystems start with the default tracing level configured to "Status" level (which includes status messages, warnings, and errors) or lower. Each trace level includes all levels below it.

A trace level of "Status" or lower will return some log information, but usually not enough for a support engineer to determine the root cause of a problem. Tracing usually must be at Notes level or higher for support engineers to troubleshoot an CIC system accurately.

Without question, logs make it easier to troubleshoot an CIC system. Genesys support professionals use logs to locate the source of system malfunctions. Customers can also view logs to examine the inner workings of the system.