GUI component log file overview

Log messages produced by Network Manager GUI components are written to log and trace files.

  • Log files provide log information in a standard format that is compatible with IBM®'s Common Base Event (CBE) format. Messages in CBE format can be used in the IBM Support Assistant Log Analyzer for offline analysis.
    Note: The IBM Support Assistant Log Analyzer is not shipped as part of IBM Tivoli Network Manager IP Edition. You must download and install it separately.
  • Trace files capture all messages a log file contains and also additional technical details of operation. Trace files are intended to aid enhanced problem resolution, and are useful to provide to your IBM support contact when requested.

Log message format

GUI log messages are recorded in text format as follows:

[<date>T<time>]:<severity>:<message_code_id>:[<thread_id>]:<message>

For example:

[2010-09-02T04:50:57]:INFO:HNMOB0001I:[Deferrable Alarm : 0]:Initialising Discovery GUI Server
Date and time
The date and time is in ISO 8601 format.
Severity
The following severity levels are available:
  • CONFIG:

    Logs all events up to and including configuration changes.

  • INFO:

    Logs only system state changes. This is the default setting.

  • WARNING:

    Logs recoverable system errors.

  • SEVERE:

    Logs unrecoverable system errors.

Message code ID
The message code provides more information on what component of the system the message originates from.
Table 1. Message code IDs
Message code ID GUI component

HNM T letter

HNM T A

HNM T B

HNM T C

Topology visualization components:

Topology client

Topology server

Topology common

HNM N letter

HNM N A

HNM N B

MIB GUI components:

MIB browser

MIB grapher

HNM O letter

HNM O A

HNM O B

Discovery GUI components:

Discovery configuration GUI

Management Database (formerly called OQL Workbench)

HNM P letter

HNM P A

Network polling GUI components:

Network polling configuration (poll policies and definitions)

HNM S letter

HNM S A

Structure view components:

Structure browser

HNM X letter

HNM X A

HNM X B

Common GUI components:

OQL interface

Others, including: Tools, Filter Builder, Widgets, Entity Search, Expressions, Tree table.

HNM Z letter

HNM Z A

External product interfaces:

Tivoli Netcool/OMNIbus Web GUI
Thread ID
The thread ID indicates the task associated with the function the message originates from.
Message
The log message itself that provides a description of the event being logged.

Trace message format

Trace messages provide more granular details about operation in the following format:

<date> <component_id>\n
<severity>: <message>

For example:

Aug 24, 2010 3:34:30 AM com.micromuse.precision.disco.server.DiscoConfigLogger
FINE: Received unknown request from the network

Trace logs do not provide standardized message format as they are for more enhanced troubleshooting purposes. The severity levels available for trace messages are as follows:

  • FINE:

    Minimum level of tracing. The majority of stack traces appear at this level already and are written to the trace file. The trace file also includes all log messages.

  • FINER:

    Medium level of tracing that provides more detailed debug messages.

  • FINEST:

    Maximum level of tracing that produces very detailed technical information.