Container Gateway logging for traffic logger
search cancel

Container Gateway logging for traffic logger

book

Article ID: 239290

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

How to push the traffic logs to STDOUT in a container gateway?

Traffic logger CWP is configured as:

trafficlogger.detail = GATEWAY_NAME=${request.time}, ${request.soap.namespace}, ${request.soap.operationname}, ${response.http.status}

Environment

Component : API GATEWAY

Cause

Traffic logger is not enabled in sample YAML files by default

Resolution

Add this below Java option to the YAML file for directing traffic log to STDOUT

-Dcom.l7tech.server.log.console.extraCats=AUDIT,LOG,TRAFFIC

** Note: You may also need to set the log levels property to info: -Dlog.console.threshold=INFO (or log.levels clusterwide property).

When you compose / build the images add extra_java_args option

For docker add the following to EXTRA_JAVA_ARGS: -Dcom.l7tech.server.log.console.extraCats=AUDIT,LOG,TRAFFIC"

Example:

  EXTRA_JAVA_ARGS: "-XX:ParallelGCThreads=4 -Dcom.l7tech.bootstrap.autoTrustSslKey=trustAnchor,TrustedFor.SSL,TrustedFor.SAML_ISSUER  -Dcom.l7tech.server.siteminder.enabled=true -Dcom.l7tech.server.disableFileLogsinks=false -Dcom.l7tech.server.log.console.extraCats=AUDIT,LOG,TRAFFIC"

Cluster Wide Properties (CWP) trafficlogger.detail : default which can be changed 

${request.time}, ${request.soap.namespace}, ${request.soap.operationname}, ${response.http.status}