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.
...
Supported log pattern formats for the PassThrough and NIO transports
| Note |
|---|
Although the WSO2 logging implementation is based on the Tomcat implementation, the set of attributes supported by the WSO2 logging implementation is different from the string replacement values supported by Tomcat. |
| Attribute | Description |
|---|---|
| Remote IP address |
| Local IP address |
| Bytes sent, excluding HTTP headers, or '-' if zero |
| Bytes sent, excluding HTTP headers |
| Cookie value |
| Accept header |
| Accept Encoding |
| Transfer Encoding |
| Remote host name (or IP address if enableLookups for the connector is false) |
| Remote logical username from identd (always returns '-') |
| Accept Language |
| Keep Alive |
| Request method (GET, POST, etc.) |
| Content Encoding |
| Request Element |
| HTTP status code of the response |
| Accept Chatset |
| Date and time, in Common Log Format |
| Content type |
| Remote user that was authenticated (if any), else '-' |
| Requested URL path |
| Local server name |
| Vary Header |
| Connection Header |
| Server Header |