About Event Attributes and Log File Format

Each event within the log file contains information about the associated application condition, including:

Event Identifier
- Type (category)
- Subtype
Timestamp
Severity Level
Details (metrics) about the event

For examples of individual events and their attribute values, see Examples of Siebel Server Log Files and Examples of Component Log Files. For an example of a group of events collected within a log file, see Example of a Detailed Component Log File.

Events are written to and collected in a log file in the order of their occurrence. Each log file contains a header that provides information on the individual log file. The following is an example of a log file header:

ï»¿2021 2017-05-07 21:02:06 0000-00-00 00:00:00 -0800 00000000 001 003f 0001 09 
SiebSrvr 2049 1364 1548 C:\siebel\ses\siebsrvr\log\siebel17.server1.log 17.0 
[xxxxx] ENU

The following table provides descriptions of the example log file header details.

Log File Header Detail	Description
`ï»¿`	Byte Order Marker (BOM). The BOM is a Unicode format instruction. If the log file header opens with characters like those shown here, then it indicates that the text editor used to view the log file cannot interpret the Unicode instruction.
`2017-05-07 21:02:06`	Timestamp of log file creation.
`-0800`	Offset of the local time from the GMT in the format ±HHMM.
`SiebSrvr`	The Siebel Server or component alias to which this log file refers.
`2049`	Task ID.
`1364`	OS Process ID (PID).
`1548`	Thread ID.
`C:\siebel\ses\siebsrv r\log\siebel17.server 1.log`	Log filename.
`17.0`	Version number.
`[xxxxx]`	Build number.
`ENU`	Language code.