ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Container Gateway logging for traffic logger

book

Article ID: 239290

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

We are seeing all the audit logs details container stdout logs

How to push the Traffic logs? We are using below CWP key value pairs and attached traffic_log.GIF configuration details.

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

Cause

Traffic logger is not enable in  sample YAML files by detail

Environment

Release : 10.0

Component : API GATEWAY

Resolution

How to get traffic logger to log into STDOUT

Adding -Dcom.l7tech.server.log.console.extraCats=AUDIT,LOG,TRAFFIC to the java options of your YAML file

When you compose / build the images add extra 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}