IBM 51 manual Logging levels, Configuring logs with log4j, Log4j.prop, Windows, Unix or Linux

Models: 51

1 248
Download 248 pages 41.4 Kb
Page 52
Image 52

Logging levels

This section details the behavior of Tivoli Intelligent Orchestrator logs based on how the logging levels are defined.

The logging level hierarchy for Tivoli Intelligent Orchestrator is shown in the following table:

Logging level

Description

 

 

msg_error#com.thinkdynamics.kanaha.

Extended for message logs

util.logging.MessageLevel

 

 

 

msg_warn#com.thinkdynamics.kanaha.

Extended for message logs

util.logging.MessageLevel

 

 

 

msg_info#com.thinkdynamics.kanaha.

Extended for message logs

util.logging.MessageLevel

 

 

 

error

Default log4j level — trace logs

 

 

warn

Default log4j level — trace logs

 

 

info

Default log4j level — trace logs

 

 

debug

Default log4j level — trace logs

 

 

The extended logging levels are the highest levels in the logging hierarchy. These levels are set exclusively for the messages, which are globalized and distinct from the trace logs. Trace logs are available only in English.

Configuring logs with log4j

Log data in Tivoli Intelligent Orchestrator is managed by log4j, an established open source logging tool. This section details the default log4j settings, the customized Tivoli Intelligent Orchestrator settings, and how you can modify settings dynamically. For complete log4j documentation, go to http://logging.apache.org/ log4j/docs/documentation.html.

The data from the console.log, msg.log, trace.log, and cbe.log files are recorded based on the default logging levels and configuration parameters set in the log4j.prop file or in the log4j-util.prop. Use the log4j-util.prop file to configure the logging for all scripts located in the %TIO_HOME%\tools directory.

log4j.prop

The log4j.prop file, shown below, defines the default configuration for message, trace, and Common Base Event logs.

The location of this file is as follows:

Windows

%TIO_HOME%\config

UNIX or Linux

$TIO_HOME/config

#output directory. Can be overwritten with -Dkanaha.logs=

kanaha.logs=logs

#message formats

#normal used to write to console.log

# error used to format error messages (prints location of a problem)

40Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide

Page 52
Image 52
IBM 51 manual Logging levels, Configuring logs with log4j, Log4j.prop, Windows, Unix or Linux