We have set rate limit for few services at policy level on the Gateway, and when the limit is reached, clients receieve the following error:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>Policy Falsified</faultstring>
<detail>
<l7:policyResult status="Service Temporarily Unavailable" xmlns:l7="http://www.layer7tech.com/ws/policy/fault"/>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
However, ssg logs do not show this error. In the debug mode, we can see message:
com.l7tech.server.message: Message was not processed: Service Temporarily Unavailable (503).
How can we see the error in the ssg log?
Gateway 11.x
The audit message:
Message was not processed: Service Temporarily Unavailable (503)
Is in INFO log level. So when Cluster wide property audit.messageThreshold=WARNING, then the message
Service Temporarily Unavailable (503)
is not logged in the ssg log.
While in the production environment, user often set threshold at WARNING level to avoid too many log information written to the ssg log. In general, user can set audit.setDetailLevel.<level> value to override the audit code log level, so the related audit code events can be logged by the log file.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/11-1/reference/gateway-cluster-properties/audit-cluster-properties.html