Log levels

Levels control which events are processed by Java™ logging. WebSphere® Application Server controls the levels of all loggers in the system.

Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。

The level value is set from configuration data when the logger is created and can be changed at run time from the administrative console. If a level is not set in the configuration data, a level is obtained by proceeding up the hierarchy until a parent with a level value is found. You can also set a level for each handler to indicate which events are published to an output device. When you change the level for a logger in the administrative console, the change is propagated to the children of the logger.

Levels are cumulative; a logger can process logged objects at the level that is set for the logger, and at all levels higher than the set level.
Table 1. Valid log levels. This table lists valid logging levels.
Level Content / Significance
Off No events are logged.
Fatal Task cannot continue and component cannot function.
Severe Task cannot continue, but component can still function
Warning Potential error or impending error
Audit Significant event affecting server state or resources
Info General information outlining overall task progress
Config Configuration change or status
Detail General information detailing subtask progress
Fine Trace information - General trace
Finer Trace information - Detailed trace + method entry / exit / return values
Finest Trace information - A more detailed trace - Includes all the detail that is needed to debug problems
All All events are logged. If you create custom levels, All includes your custom levels, and can provide a more detailed trace than Finest.
For instructions on how to set logging levels, read the topic about configuring Java logging using the administrative console.
Note: Trace information, which includes events at the Fine, Finer and Finest levels, can be written only to the trace log. Therefore, if you do not enable diagnostic trace, setting the log detail level to Fine, Finer, or Finest does not effect the logged data.

指出主題類型的圖示 參照主題



時間戳記圖示 前次更新: July 9, 2016 11:13
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rtrb_loglevels
檔名:rtrb_loglevels.html