WildFly Logging Subsystem Concepts: Difference between revisions
No edit summary |
|||
| Line 22: | Line 22: | ||
A logging profile is a named set of logging configurations, which can be created and assigned to applications. | A logging profile is a named set of logging configurations, which can be created and assigned to applications. | ||
=Boot Logging= | |||
Details about the Java environment and component service startup are logged during the JBoss instance startup in the server.log file. The configuration of boot logging is specified in the configuration file logging.properties. The location of the configuration file defense on the mode in which JBoss runs ($JBOSS_HOME/standalone/configuration/logging.properties, $JBOSS_HOME/domain/configuration/logging.properties for the domain controller and $JBOSS_HOME/domain/servers/<server-name>/data/logging.properties. | |||
logging.properties is active until the logging subsystem is started and takes over. | |||
Revision as of 23:44, 19 October 2016
External
- EAP 6 Administration and Configuration Guide - The Logging Subsystem https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/chap-The_Logging_Subsystem.html
Internal
Overview
The logging subsystem is based on JBoss LogManager and supports several third-party application logging frameworks, in addition to JBoss Logging: Apache Commons Logging, Simple Logging Facade for Java (SLF4J), Apache log4j and Java SE logging (java.util.logging).
Category
A log category defines what messages to capture.
Handler
A log handler defines how to deal with generated log messages.
Logging Profile
A logging profile is a named set of logging configurations, which can be created and assigned to applications.
Boot Logging
Details about the Java environment and component service startup are logged during the JBoss instance startup in the server.log file. The configuration of boot logging is specified in the configuration file logging.properties. The location of the configuration file defense on the mode in which JBoss runs ($JBOSS_HOME/standalone/configuration/logging.properties, $JBOSS_HOME/domain/configuration/logging.properties for the domain controller and $JBOSS_HOME/domain/servers/<server-name>/data/logging.properties.
logging.properties is active until the logging subsystem is started and takes over.