This article will discuss why some log entries are present in the API Gateway logs but not on a syslog server, and how to get it to work as expected. This article will assume that a syslog connection is already created. If a syslog connection hasn't yet been created, please review the documentation for doing so.
For example, the following log entry is present in the API Gateway, and needs to see it on the syslog server too but currently is not seen in the syslog server:
2020-06-16T19:32:00.052+0000 WARNING 1104 com.l7tech.server.policy.assertion.ServerHttpRoutingAssertion: 4042: Problem routing to http://localhost:8081/contest2. Error msg: Unable to obtain HTTP response from http://localhost:8081/contest2: Read timed out. Timed out at 30000ms
This article applies to all supported API Gateway versions with a Syslog server connection setup.
If the log entry is not seen in the syslog server, it's because there are filters getting in the way on the log sink properties.
Remove or add any filters needed to allow the log entry to be present on the syslog server too. This includes the following areas for review:
If it is felt that the configuration is correct on the syslog setup but are still not seeing what is expected on the syslog server, then please open a support case with Broadcom Support and ensure to include the following details when doing so: