-
Notifications
You must be signed in to change notification settings - Fork 1
Logging
Loader contains a category based logger. Events in the system are categorized and sent to the log appenders which handle those events.
When an event is enabled, no other events are affected. It is therefore possible to enable trace logging without having to enable debug logging. It is possible to only generate debug events and not generate any other category of events.
This category of events allows one to trace the execution path through the system. This is normally the first level of debugging a system, tracing execution through the components. As the thread of execution passes through components, trace events are logged to indicate when and where processing occurs. Reading through trace events show the progression of a thread of execution through the system. Note: operational state details are seldom logged in trace events; only logical steps in the execution path.
Detailed data related to operation is output in debug events. These events contain values of variables and data exchanged between components. The operational state of components are normally logged in debug events. While is is possible to ascertain the flow of a system with the events in a debug log, the data in the events are designed to support tracing execution flow and the operational data which existed when the thread of execution was at any particular point.
Events from which the system cannot recover.
Events which cause the transaction to fail, but the system will continue to operate.
Events which will result in unexpected results, but the transaction will recover.
Informational events to assist the user in ascertaining the state of the system and to provide operational feedback.