Logging; Controlling What Is Logged; Event Log Format - TANDBERG Gatekeeper User Manual

TANDBERG Gatekeeper User Manual

12 Logging

The Gatekeeper provides logging for troubleshooting and auditing purposes.
The event log may be viewed from the command line by using the eventlog command, specifying
the number of lines to display. Alternatively the web page System Status
used.

12.1 Controlling what is logged

You can control the verbosity with which the Gatekeeper logs information. All events have an
associated level in the range [1-3]. Level 1 refers to high level events such as registration requests
and call attempts. Level 2 events are recorded for incoming and outgoing message - H.323,
LDAP etc excluding noisy messages such as H.460.18 keep-alives and H.245 video fast-updates.
. Level 3 events include some of these noisy events. By default, logging is set to level 1.

12.2 Event log format

The event log is displayed in an extension of the UNIX syslog format:
date time host name facility name <PID>:
date and time represent the local time at which the message was logged. host name is the name
of the system generating the log message, facility — the name of the program generating the log
message — will be tandberg for all messages originating from TANDBERG processes, but will
differ for messages from third party processes which are used in the Gatekeeper product.
For all messages logged from the tandberg process the message details field is structured to
allow easy parsing. It consists of a number of human-readable name=value pairs, separated by
a space. The first two fields are always:
Field Example
Time
Time=2006/20/01-14:02:17
Event
Event=RegistrationRequest
and the last field of the message is always the event level:
Field Example Description
Level The level of the event being logged.
Level=1
44
message details
Description
The UTC date and time at which the event was
generated.
The event which caused the log message to
be generated.
Event Log may be