Siebel System Monitoring and Diagnostics Guide > Configuring Siebel Server and Component Logging > About Configuring Siebel Server and Component Logging >

About Events and Event Logging

The elements of event logging are defined in the following bullets:

• Event. An event is created each time you execute a program code (such as running a task).
• Event Type. Event types are categories of events.
  • For information on event types pertinent to a specific part of Siebel Business Applications, see product-specific documentation or details available on My Oracle Support.

    NOTE:  The Siebel Bookshelf is available on Oracle Technology Network (OTN) and Oracle Software Delivery Cloud. It might also be installed locally on your intranet or on a network location.

  • For generic event types used in server component and Siebel Application Object Manager diagnostics, see Common Event Types for Component Diagnostics and Common Event Types for Siebel Application Object Manager Diagnostics.
• Event Subtype. Event subtypes are code references that define the event.
• Log Level. The log level determines the amount of information that is written to the log file. Log levels are set for event types. Table 17 lists the log levels of event types.
• Severity. A severity level is associated with each event subtype. The severity level and log level share the same scale and are compared when writing events to the log file. Table 17 lists the severity of event subtypes.

  Table 17. Severity and Log Levels

  Log and Severity Level	Description
  0	Fatal
  1	Errors
  2	Warnings
  3	Informational
  4	Details
  5	Diagnostic

When an event occurs, the severity level of the event (as defined by the event subtype) is compared with the log level of the event type. If the numerical value of the event severity level is equal to or lower than the numerical value of the event type log level, then the event is written to the log file. If the numerical value of the event severity level is higher than the numerical value of the event type log level, then the event is ignored.

NOTE:  Event subtypes with a lower numeric value have a higher severity. For example, a value of 0 indicates the event subtype is more severe than one with a value of 5. By setting the event log level to a low number such as 1, only the most severe events are logged, but if the event log level is set to a higher number such as 5, more information is captured including less severe event subtypes.

For example, the Siebel Server components in the Enterprise Application Integration component group (alias EAI) have an event type called EAI Siebel Wizard. Several event subtypes belong to the EAI Siebel Wizard event type, including:

• EAI Siebel Wizard Invalid Business Component with a severity level of 2
• EAI Siebel Wizard Invalid MVG with a severity level of 2
• EAI Siebel Wizard MVG with a severity level of 3

While the EAI component group is running, the process encounters a multi-value group (MVG). This encounter creates an event of the EAI Siebel Wizard MVG subtype. If the MVG is invalid, a second event of the EAI Siebel Wizard Invalid MVG subtype is created. If the log level of the EAI Siebel Wizard event type is set to 1, both events are ignored. If the log level is set to 3, both events are written to the log file.

Events are logged at the Siebel Server level and the component level. For details on Siebel Server events, see Configuring Siebel Server Logging. For information on component events, see Configuring Siebel Server Component Logging.