Page Comparison

...

• Manually editing the log4j.properties file.

• If you are using a WSO2 Carbon product, you can configure logging through the management console. These changes will be applied at run time. See your product's documentation for details.
  

  Info

  In WSO2 products, using the management console is recommended, because all changes made to log4j through the management console persist in the WSO2 Registry. Therefore, those changes will be available after the server restarts. Changes that you make to the logging configuration via the management console will get priority over what is defined in the actual log4j.properties file. However, if you modify the log4j.properties file and restart the server, the earlier log4j configuration that persisted in the registry will be overwritten. There is also an option in the management console to restore the original log4j configuration from the log4j.properties file.

...

• Through the log files that are stored in the <PRODUCT_HOME>/repository/logs folder. This folder contains current logs in a log file with a date stamp. Older logs are archived in the wso2carbon.log file.
• 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.