...
Logging is one of the most important aspects of a production-grade server. A properly configured logging system is vital for identifying errors, security threats and usage patterns. All WSO2 products are shipped with the log4j logging capabilities, which generates administrative activities and server side logs. The log4j.properties file, which governs how logging is performed by the server can be found in the <PRODUCT_HOME>/repository/conf directory.
Note that in addition to the logs from libraries that use Log4j, all logs from libraries (such as, Tomcat, Hazelcast and more) that use Java logging framework are also visible in the same log files. WThat is, when Java logging is enabled in Carbon, only the Log4j appenders will write to the log files. If the Java Logging Handlers have logs, these logs will be delegated to the log events of the corresponding Log4j appenders. A Pub/Sub registry pattern implementation has been used in the latter mentioned scenario to plug the handlers and appenders. The following default log4j appenders are in the log4j.properties file are used for this implementation:
...
Configuring products for logging
The log4j.properties file, which governs how logging is performed by the server can be found in the <PRODUCT_HOME>/repository/conf directory. Given below are ways to configure log4j files:
...
There are several ways to view system and application logs of a running Carbon instance can be viewed as described below.
- Through the log files that are stored in the
<PRODUCT_HOME>/repository/logsfolder. This folder contains current logs in a log file with a date stamp. Older logs are archived in thewso2carbon.logfile. - Through the command prompt/shell terminal that opens when you run the "
wso2server.bat"/"wso2server.sh" files to start the Carbon server. - If you are using a WSO2 product, logs can be viewed and monitored through the product's management console. See the product's documentation for details.
...