Skip to content

Commit

Permalink
Merge pull request #8208 from vishmi49/vishmi_master_docs
Browse files Browse the repository at this point in the history
[master Update Docs on Wirelogs
  • Loading branch information
tharikaGitHub authored Jul 17, 2024
2 parents 3e49be6 + 57104b9 commit 29ce292
Showing 1 changed file with 7 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -188,8 +188,8 @@ The following is a sample Gateway Wire Log for an API request.

### Enabling the Gateway Wire Logs

1. Open the `<API-M_HOME>/repository/conf/log4j2.properties` file.
2. Locate the `synapse-wire` logger, which is already defined in the default `log4j2.properties` file.
1. Open the `<API-M_HOME>/repository/conf/log4j2.properties` file.
2. Locate the `synapse-wire` logger, which is already defined in the default `log4j2.properties` file.

```
logger.synapse-wire.name = org.apache.synapse.transport.http.wire
Expand All @@ -203,7 +203,7 @@ The following is a sample Gateway Wire Log for an API request.
logger.synapse-headers.level = DEBUG
```
3. Append the `synapse-wire` logger name to the `loggers` configuration which is a comma separated list of all the active loggers.
3. Append the `synapse-wire` logger name to the `loggers` configuration which is a comma separated list of all the active loggers.
```
loggers = synapse-wire, trace-messages, org-apache-coyote,com-hazelcast
Expand All @@ -215,7 +215,10 @@ The following is a sample Gateway Wire Log for an API request.
loggers = synapse-headers, trace-messages, org-apache-coyote,com-hazelcast
```
4. Observe the logs for incoming and outgoing traffic in the `<API-M_HOME>/repository/logs/wso2carbon.log` file.
4. Observe the logs for incoming and outgoing traffic in the `<API-M_HOME>/repository/logs/wso2carbon.log` file.
!!! Limitation
If synapse-wire logs are enabled during high load, outgoing traffic between the gateway and the backend will not be printed in the `wso2carbon.log` file. This happens when the backend connection is keep alive. As we are maintaining connections in a connection pool, the same connections will be reused in keep alive mode irrespective of the changes done in the `log4j2.properties` file.
## HTTP Access Logs
Expand Down

0 comments on commit 29ce292

Please sign in to comment.