This documentation is for WSO2 Enterprise Service Bus version 4.9.0 . View documentation for the latest release.
||
Skip to end of metadata
Go to start of metadata

Application logs are where events invoked by an application or a program running in a system are recorded. Similarly, the Application Logs of a running Carbon instance display the log events of its deployed Web applications and Web services. The "Application Logs" page has been introduced as a fine-grained view of System Logs. While system logs display log events of the entire system holistically, the application logs page allows the user to select a particular application and view its logs only.

The application logs show logs from the proxy service, not from any logs inside its sequences. To view logs from the log mediator, see System Logs.

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).

For more information on logs and how to change log properties according to your preferences, refer to section Logging. Follow the instructions below to access statistics on Application Logs.

1. Log on to the product's management console and select "Monitor -> Application Logs."

2. The "Application Logs" page appears. This page displays logs of a selected application in a bottom-up manner. For example,


Note

The log messages displayed on this page are obtained from a memory appender. Therefore, 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, refer to http://logging.apache.org/log4j

  3. You can see a drop-down list from which a deployed Web Services or a Web applications can be selected to view its log files.


4. In the "View" list, select the category of logs you want to view. The available categories are:

  • TRACE - Trace messages.
  • DEBUG - Debug messages.
  • INFO - Information messages.
  • WARN - Warning messages.
  • ERROR - Error messages.
  • FATAL - Fatal error messages.
  • ALL - Displays all categories of logs.

For example,


5. You can also find a certain log using the search function. Enter a keyword (or part of a keyword) and click "Search." When a search criteria is given, the "View" is displayed as "Custom".

For example,


Note

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

  • No labels