The advantage of having per-API log files is that it is very easy to analyze/monitor what went wrong in a particular REST API defined in the ESB by looking at the log files. The API log is an additional log file, which will contain a copy of the logs to a particular REST API.
...
| Anchor | ||||
|---|---|---|---|---|
|
Add the following section to the end of the file to configure the logger for log messages where the Log Category is INFO.
| Code Block |
|---|
log4j.category.API_LOGGER=INFO, API_APPENDER
log4j.additivity.API_LOGGER=false
log4j.appender.API_APPENDER=org.apache.log4j.RollingFileAppender
log4j.appender.API_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-api${instance.log}.log
log4j.appender.API_APPENDER.MaxFileSize=1000KB
log4j.appender.API_APPENDER.MaxBackupIndex=10
log4j.appender.API_APPENDER.layout=org.apache.log4j.PatternLayout
log4j.appender.API_APPENDER.layout.ConversionPattern=%d{ISO8601} [%X{ip}-%X{host}] [%t] %5p %c{1} %m%n</pre>
|
...
| Tip |
|---|
The in-sequence of the REST API will need to contain a Log mediator with with the Log Category defined as DEBUG to be able to view logs in the log file. |
...