...
org.wso2.carbon.logging.appenders.CarbonConsoleAppenderorg.wso2.carbon.logging.appenders.CarbonDailyRollingFileAppender
See the following topics on this page for details:
| Table of Contents | ||||
|---|---|---|---|---|
|
Configuring products for log monitoring
...
The log4j-based logging mechanism uses appenders to append all the log messages into a file. That is, at the end of the log rotation period, a new file will be created with the appended logs and archived. The name of the archived log file will always contain the date on which the file is archived.
...
Monitoring logs
In each Carbon product, users can configure and adjust the logging levels for each type of activity/ transactions. There are several ways to view system and application logs of a running Carbon instance.
- 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. - Through the advanced monitoring capabilities in WSO2 BAM.
- Through the Management Console. See Monitoring Logs for details.management console of your product. This option is only available if the Logging Management feature is installed in your product.
Logging Management Feature
The possibility to use the management console of your product for log configuration and log monitoring is provided by the following feature in the WSO2 feature repository:
...
If the above feature is not bundled in your product by default, you can install it using the instructions given in the Feature Management section.