Container GW is very chatty. Our log sink allowed a lot of filters for customers, but Container GW logging (Console Logging) is very chatty and it clutters the log utility that provides the log data to the help desk.
How can this be minimized to include traffic logger?
Release : 10.1
Component : API GATEWAY
First configured gateway where NO logging is occurring, then work backwards adding each package to get the desired info:
How too:
Simple endpoint /route1 that contains the two assertions:
“Audit Messages in Policy” set to INFO (should not record when level is WARNING)
“Audit Details” set to log @ level INFO
Cluster Wide Properties (CWP)
audit.adminThreshold: WARNING (note prevents policy updates from logging)
audit.messagesThreshold: WARNING ( warning level that affect the audit message in policy assertions from logging anything, if change to info logging occurs)
log.console.threshold: INFO
log.levels:
com.l7tech.level = WARNING
com.l7tech.server.policy.assertion.level= WARNING
com.l7tech.traffic.level = WARNING
Make a results: http://<Gateway_Host>:8080/route1
Results NOTHING logged at all
Change log.levels:
com.l7tech.level = WARNING
com.l7tech.server.policy.assertion.level= WARNING
com.l7tech.traffic.level = INFO
Make a results: http://<Gateway_Host>:8080/route1
Results ONLY one entry logged Traffic Logger
# docker logs -f gateway101_api-gateway_1
2022-04-12T14:19:16.384+0000 INFO 534 com.l7tech.traffic: GATEWAY_NAME=Gateway5|CORRELATION_ID=|ENTRY_TIME=|APP_LOB=|APP_NAME=|HTTP_METHOD=GET|SERVICE_NAME=Route-1|REQUEST_URL=http://<gatewayhost>.net:8080/route1|API_CODE=|REQUEST_HEADERS=|REQUEST_Cookies=|REQUEST_BODY=|RESPONSE_HEADERS=|RESPONSE_BODY=|REMOTE_IP=<ip_address>|EXIT_TIME=2022-04-12T14:19:16.383Z|TOTAL_ROUTING_TIME=323|TOTAL_ELAPSED_TIME=334|REQUEST_CONCURRENCY=1|STATUS=|CONSUMER=
Change log.levels:
com.l7tech.level = WARNING
com.l7tech.server.policy.assertion.level= INFO
com.l7tech.traffic.level = INFO
Make a results: http://<Gateway_Host>:8080/route1
Results the traffic logger AND the Audit details (set to INFO) is displayed
# docker logs -f gateway101_api-gateway_1
2022-04-12T14:21:29.645+0000 INFO 558 com.l7tech.server.policy.assertion.ServerAuditDetailAssertion: -4: GATEWAY_NAME_AUDIT_DETAIL=Gateway5|CORRELATION_ID=|ENTRY_TIME=|APP_LOB=|APP_NAME=|HTTP_METHOD=GET|SERVICE_NAME=Route-1|REQUEST_URL=http://<gatewayhost>:8080/route1|API_CODE=|REQUEST_HEADERS=|REQUEST_Cookies=|REQUEST_BODY=|RESPONSE_HEADERS=|RESPONSE_BODY=|REMOTE_IP=<ip_address>|EXIT_TIME=2022-04-12T14:21:29.644Z|TOTAL_ROUTING_TIME=323|TOTAL_ELAPSED_TIME=329|REQUEST_CONCURRENCY=1|STATUS=|CONSUMER=
2022-04-12T14:21:29.646+0000 INFO 558 com.l7tech.traffic: GATEWAY_NAME=Gateway5|CORRELATION_ID=|ENTRY_TIME=|APP_LOB=|APP_NAME=|HTTP_METHOD=GET|SERVICE_NAME=Route-1|REQUEST_URL=http://<gatewayhost>:8080/route1|API_CODE=|REQUEST_HEADERS=|REQUEST_Cookies=|REQUEST_BODY=|RESPONSE_HEADERS=|RESPONSE_BODY=|REMOTE_IP=<ip_address>|EXIT_TIME=2022-04-12T14:21:29.646Z|TOTAL_ROUTING_TIME=323|TOTAL_ELAPSED_TIME=331|REQUEST_CONCURRENCY=1|STATUS=|CONSUMER=