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.

...

1. Open the <EI_HOME>/conf/tomcat/catalina-server.xml file (which is the server descriptor file for the embedded Tomcat integration) 

2. Customize the attributes for the Access_Log_Valve variable shown below. 

   Code Block
   <Valve className="org.apache.catalina.valves.AccessLogValve" directory="${carbon.home}/repository/logs" prefix="http_access_management_console_" suffix=".log" pattern="combined" />

   The attributes that are used by default are explained below. See the descriptions of the Tomcat-supported Access Log Valve attributes and customize the required values.

   directory	The path to the directory that will store the access log file. By default, this location is set to "${carbon.home}/repository/logs" in all WSO2 products.
   prefix	The prefix added to the log file's name. By default, this is "http_access_management_console_".
   suffix	The suffix added to the log file's name. By default, this is ".log".
   pattern	The attribute defines the format for the log pattern, which consists of the information fields from the requests and responses that should be logged. The pattern format is created using the following attributes: A standard value to represent a particular string. For example, "%h" represents the remote host name in the request. See the list of string replacement values supported by the Tomcat valve. %{xxx}i is used to represent the header in the incoming request (xxx=header value). %{xxx}o is used to represents the header in the outgoing request (xxx=header value). While you can use the above attributes to define a custom pattern, the standard patterns shown below can be used. common (Apache common log pattern): Code Block pattern=%h %l %u %t "%r" %s %b combined (Apache combined log pattern): Code Block pattern=%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i" Note that, by default, the "combined" pattern is enabled in the ESB.

3. Restart the server. According to the default configurations, a log file named http_access_management_console_.{DATE}.log  is created inside the <EI_HOME>/repository/logs  directory. The log is rotated on a daily basis.

...

1. Change the log level from WARN to INFO for the following entry in the <EI_HOME>/conf/log4j.properties configuration file.

   Code Block
   language xml
   log4j.logger.org.apache.synapse.transport.http.access=INFO

2. You can customize the format of this access log by changing the following property values in the <EI_HOME>/conf/access-log.properties configuration file. If this file does not exist in the product by default, you can create a new file with the following parameters.

   access_log_directory	Add this property ONLY if you want to change the default location of the log file. By default, the product is configured to store access logs in the <EI_HOME>/repository/logs directory.
   access_log_prefix	The prefix added to the log file's name. The default value is as follows: Code Block access_log_prefix=http_access_
   access_log_suffix	The suffix added to the log file's name. The default value is as follows: Code Block access_log_suffix=.log
   access_log_file_date_format	The date format used in access logs. The default value is as follows: Code Block access_log_file_date_format=yyyy-MM-dd
   access_log_pattern	The attribute defines the format for the log pattern, which consists of the information fields from the requests and responses that should be logged. The pattern format is created using the following attributes: A standard value to represent a particular string. For example, "%h" represents the remote host name in the request. Note that all the string replacement values supported by Tomcat are NOT supported for the PassThrough transport's access logs. The list of supported values are given below. %{xxx}i is used to represent the header in the incoming request (xxx=header value). %{xxx}o is used to represents the header in the outgoing request (xxx=header value). While you can use the above attributes to define a custom pattern, the standard patterns shown below can be used. common (Apache common log pattern): Code Block access_log_pattern=%h %l %u %t "%r" %s %b combined (Apache combined log pattern): Code Block access_log_pattern=%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i" By default, a modified version of the Apache combined log format is enabled in the ESB as shown below. Note that the "X-Forwarded-For" header is appended to the beginning of the usually combined log format. This correctly identifies the original node that sent the request (in situations where requests go through a proxy such as a load balancer). The "X-Forwarded-For" header must be present in the incoming request for this to be logged. Code Block access_log_pattern=%{X-Forwarded-For}i %h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-Agent}i\"

3. Restart the server. 

4. Invoke a proxy service or REST API that is deployed in the ESB. For testing purposes, use the artifacts in the quick start guide. 
   The access log file for the service/API will be created in the <EI_HOME>/repository/logs directory. The default name of the log file is http_access_.log.

   Tip
   Note that there will be delay in printing the logs to the log file.

Supported log pattern formats for the PassThrough and NIO transports

%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