...
- Name - The name of an appender. By default, WSO2 ESB comes API Manager comes with the following log appenders configured:
- CARBON_CONSOLE - Logs to the console when the server is running.
- CARBON_LOGFILE - Writes the logs to the
<ESB<API-M_HOME>/repository/logs/wso2-esbwso2carbon.logfile. - SERVICE_APPENDER - Writes mediation time audit messages to the <
ESBAPI-M_HOME>/repository/logs/wso2-esbapigw-service.logfile. - TRACE_APPENDER - Writes mediation time tracing/debug messages to the <
ESBAPI-M_HOME>/repository/logs/wso2-esbapigw-trace.logfile for tracing enabled services. - TRACE_MEMORYAPPENDER
- CARBON_MEMORY
- CARBON_SYS_LOG - Allows separation of the software that generates messages from the system that stores them and the software that reports and analyzes them.
- Log pattern - Defines the output format of the log file.
- Threshold - Filters log entries based on their level. For example, if the threshold is set to WARN, log entries are allowed to pass into the appender if its level is WARN, ERROR or FATAL, while other entries are discarded.
...
Alternatively, you can uncomment the entry for the two loggers as follows:
- Go to the
<ESB<API-M_Home>HOME>/repository/confdirectory and open thelog4j.propertiesfile with a text editor. - Edit the entries for the two loggers as follows by removing the commented (#).
log4j.logger.org.apache.synapse.transport.http.headers=DEBUGlog4j.logger.org.apache.synapse.transport.http.wire=DEBUG - Save the changes.