This documentation is for WSO2 API Manager 2.1.0. View documentation for the latest release.

All docs This doc

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reviewed

Logging is one of the most important monitoring tools of a production server. A properly configured logging system is vital for identifying errors, security threats, and usage patterns. WSO2 API Manager uses a log4j based logging mechanism through the Apache Commons Logging facade library. The file, which governs how logging is performed by the server, is in the API-M_HOME/repository/conf directory. In general, you should not modify should not modify the directly file directly. Instead, you set up and modify logging using the ESB management console. The settings in the management console override the settings in in the file.

A logger is used to log messages for a specific system or application component. Loggers are normally named using a hierarchical, dot-separated namespace and have a “childchild-parent” parent relationship. For example, the logger named "named" is  is a parent of the logger named "named" and  and a child of “rootof root.

The following topics provide more information about logging: