Page Comparison

HTTP access logs help you monitor information such as the persons who access the product, how many hits are received, what the errors are, etc. This information is useful for troubleshooting errors.

All WSO2 products can enable access logs for the HTTP servlet transport. This servlet transport works on 9443/9763 ports, and it receives admin/operation requests. Therefore, access logs for the servert transport is useful for analysing operational/admin-level access details. Additionally, in products such as WSO2 Enterprise Service Bus, WSO2 Enterprise Integrator (and WSO2 API Manager), access logs can be generated for the PassThrough and NIO transports. The PassThrough/NIO transports works on 8280/8243 ports and is used for API/Service invocations. By default, the access logs from both the servlet transport and the PassThrough/NIO transports are written to a common access log file located in the <EI_HOME>/repository/logs/ directory.

...

...

Note that access logs for the HTTP servlet transport logs details of the request as well as the response on a single log line. However, the access logs for the PassThrough transport logs the request and the response on two separate log lines.

See the topics given below to configure the default behaviour of HTTP access logs in the ESB.

Configuring access logs for the HTTP servlet transport

As the runtime of WSO2 products is based on Apache Tomcat, you can use the Access_Log_Valve variable in Tomcat as explained below to configure access logs for the HTTP servlet transport:

...

Configuring access logs for the PassThrough and NIO transports (Service/API invocation)

By default, access logs related to service/API invocation are disabled for performance reasons in the above products. You should enable these access log only for troubleshooting errors. Follow the steps given below to enable access logs for the PassThrough transport:

...

%a

%A

%b

%B

%c

%C

%e

%E

%h

%l

%L

%k

%m

%n

%r

%s

%S

%t

%T

%u

%U

%v

%V

%x

%Z