Log Messages File Format

Table 6 lists the log message format and descriptions.

Table 6. Log Message Format

Log Message FormatDescription

Time Stamp

Date and time when the message was generated, adjusted for time difference between the host where the message was generated and the host of the common repository. This field is set only when the log message is written to a central repository and should not be set by components. Example: [2010-01-22T05:23:31.755-08:00]

Component ID

The component that originated the message. Example: [FoundationServices0].

Message Type

Defined message types: ERROR, WARNING, NOTIFICATION, and TRACE. The value UNKNOWN may be used when the type is unknown.

  • ERROR—A serious problem that requires immediate attention from the System Administrator and is not caused by a bug in the product.

  • WARNING—A potential problem that should be reviewed by the System Administrator.

  • NOTIFICATION—A major lifecycle event such as the activation or deactivation of a primary subcomponent or feature.

  • TRACE—Trace or debug information for events that are meaningful to users, such as public API entry/exit points. The messages should be understandable by those who do not know internal implementation details.

  • UNKNOWN (may be used when the type is unknown).

Message ID

A short identifier that uniquely identifies the message. Example: [EPMWKSP-000001]

Module ID

An identifier of the module that originated the message. The value is component specific. Example: [Initialization]

Execution Context Id (ECID)

Execution context ID helps connect multiple log files. Example: [ecid: 0000IPMCrhW17ic5PjWByd1BMQPg000002,0]

Message text

Actual log message