Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ambassador pods displaying log level info DESPITE setting AES_LOG_LEVEL to error and envoy_log_path to null #11

Closed
muhanator opened this issue Aug 5, 2021 · 1 comment

Comments

@muhanator
Copy link

muhanator commented Aug 5, 2021

I am trying to set the log level of my Ambassador deployment to error.

  1. I first tried setting the environment variable AES_LOG_LEVEL to error as specified in the documentation (https://www.getambassador.io/docs/edge-stack/latest/topics/running/aes-extensions/#aes_log_level) but the logs still remained of log level info.
env:
  AES_LOG_LEVEL: error
  AMBASSADOR_CERTS_SINGLE_NAMESPACE:

I even went inside the pod to make sure that environment variable AES_LOG_LEVEL was set to error and it was.

  1. So then I believed I had to change the Envoy debug logs and so by following (https://www.getambassador.io/docs/edge-stack/latest/topics/running/ambassador/#envoy), I set "envoy_log_path: /dev/null" for my module. Yet, my logs still display logs of level info.
service:
  externalTrafficPolicy: 'Local'
  annotations:
    service.beta.kubernetes.io/azure-load-balancer-internal: 'true'
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: Module
      name: ambassador
      config:
        service_port: 8443
        use_remote_address: true
        buffer:  
          max_request_bytes: 10485760
        x_num_trusted_hops: 1
        x_forwarded_proto_redirect: true
        grpc_stats:
          upstream_stats: true
          all_methods: true
        envoy_log_path: /dev/null
    external-dns.alpha.kubernetes.io/hostname: '${serviceVariable.ambassador_domain}'

Despite both of these changes, my logs appear as so:

2021-08-05 18:29:17 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_29] INFO: 0CE05326-EE6E-4B9D-8613-9A9D2FAD71C1: 10.58.131.14 "GET /metrics" 16ms 200 success
2021-08-05 18:29:21 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_28] INFO: BA21CC1A-BC73-4096-8EA6-2708AA4F6089: 10.58.131.18 "GET /metrics" 13ms 200 success
2021-08-05 18:29:22 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_3] INFO: 05288778-EF15-4A89-B6BC-B5F4AD0DB762: 10.58.131.14 "GET /metrics" 16ms 200 success
2021-08-05 18:29:26 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_22] INFO: 9B2F7A08-FBA8-4CEA-8558-95C938F65B2F: 10.58.131.18 "GET /metrics" 13ms 200 success
2021-08-05 18:29:27 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_24] INFO: F7BA0E95-BCA9-40BD-839B-CDC992CAD796: 10.58.131.14 "GET /metrics" 16ms 200 success
2021-08-05 18:29:31 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_15] INFO: 8CFBC403-7579-4421-86FA-095D4609DC70: 10.58.131.18 "GET /metrics" 14ms 200 success
2021-08-05 18:29:32 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_23] INFO: 53E9D092-58C4-4D0A-9A04-D14B7604C4F4: 10.58.131.14 "GET /metrics" 15ms 200 success
2021-08-05 18:29:36 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_8] INFO: 6F401082-76C2-4A1A-B3FB-7BDE8495D4C0: 10.58.131.18 "GET /metrics" 16ms 200 success
2021-08-05 18:29:37 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_28] INFO: 51C0FE1F-A92F-4C2F-8F8B-2607810D6A35: 10.58.131.14 "GET /metrics" 17ms 200 success
2021-08-05 18:29:40 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_18] INFO: 4DCAE8C6-C0FD-4C40-9CDA-2C325CC01984: 10.58.131.18 "GET /metrics" 14ms 200 success
2021-08-05 18:29:42 diagd 1.8.1-21-g77f6ec45e-dirty [P146TThreadPoolExecutor-0_20] INFO: 4E89C44C-5793-45C4-91B4-EE3205C1902E: 10.58.131.14 "GET /metrics" 17ms 200 success

I believe I did everything specified from the documentation, can you please help me change the logs to level error.

@muhanator
Copy link
Author

marked as duplicate: emissary-ingress/emissary#3666

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant