emissary icon indicating copy to clipboard operation
emissary copied to clipboard

TCP logging is not there on ambassador

Open kannanvr opened this issue 4 years ago • 10 comments

Describe the bug When we have configured HTTP/HTTPS, we can see all the logs related to the incoming connection on ambassador pod. But For TCP connection, we could not get the logs at all.

To Reproduce Steps to reproduce the behavior: Folowing is my ambassador deployment container yaml

      - name: ambassador
        image: quay.io/datawire/ambassador:1.3.0
        imagePullPolicy: "IfNotPresent"
        resources:
          limits:
            cpu: 1
            memory: 400Mi
          requests:
            cpu: 200m
            memory: 100Mi
        env:
        - name: AMBASSADOR_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: APP_LOG_LEVEL
          value: trace
        - name: AES_LOG_LEVEL
          value: trace
        - name: SCOUT_DISABLE
          value: "1"

I have enabled AES_LOG_LEVEL and APP_LOG_LEVEL. But when i am adding the TCPMAPPING on a annotations of service , TCP connection is working fine. But We need logs to debug the connection.

apiVersion: v1
kind: Service
metadata:
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: TCPMapping
      name: postgres-1
      port: 5633
      service: postges-ingress.postges1:5432

We are expecting the TCP log when we establish the TCP connection through Ambassador

Expected behavior We are expecting the TCP log when we establish the TCP connection through Ambassador

Versions (please complete the following information):

  • Ambassador: 1.3.0
  • Kubernetes Version 1.15.3

kannanvr avatar Aug 27 '20 05:08 kannanvr