This documentation is for WSO2 Business Rules Server 2.1.0.View documentation for the latest release.
Skip to end of metadata
Go to start of metadata

The System Logs page displays all events of a running a Carbon instance. Further, it facilitates downloading and viewing log files according to user preferences. The log files can be retrieved in two ways:

  • If syslog-ng is configured, log files are taken from the remote location where the log files are hosted using syslog-ng server. 
  • If syslog-ng is not configured, log files are taken from the local file system (super-tenant or Stand-alone apps).

More information about  logs and how to set log properties is available in the Logging section. Statistics on system logs are provided by the following feature:

Name : WSO2 Carbon - Logging Management Feature
Identifier :

If it is not bundled in your product by default, you can install the above feature by following the instructions in the Feature Management section.  

Follow the instructions below to access statistics on system logs.

  1.  Log on to the product's management console and click Monitor on the navigation bar to the left. Then click System Logs. The System Logs page appears.  The logs are displayed in a bottom-up manner as follows.

    The log messages displayed on this page are obtained from a memory appender. Hence, the severity (log level) of the displayed log messages are equal to or higher than the threshold of the memory appender. For more information on appenders, loggers, their log levels and logging, see

  2. To view archived logs, click the Show Archived tab at the bottom of the System Logs page. The archived logs are displayed as follows. Click Download to download the wso2carbon.log file in <PRODUCT_HOME>/repository/logs.

  3. To view logs belonging to a specific category at a given time, select the required category in the View field.

    The available categories are:
    • TRACE - Trace messages.
    • DEBUG - Debug messages.
    • INFO - Information messages.
    • WARN - Warning messages.
    • ERROR - Error messages.
    • FATAL - Fatal error messages.

  4. To find a specific log, enter a keyword (or a part of a keyword) in the Search Logs field and click Search.


    The location of the log files on disk is specified in the log4j.configuration file.


  • No labels