-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Consul global proxy configuration not propagating to the proxies #21986
Comments
Additional info, i was able to get the access logs on the health checks and admin access, but not on the service-service communication. Is there something I'm missing on my setup? Example access logging:
I was expecting to have logs from services communicating with the other services using the Envoy proxy 🤔 Any help is appreciated, thanks! |
Consul global proxy configuration not propagating to the envoy proxies configured via consul connect:
I've a service mesh on ECS with EC2 working as the control plane where my consul server is installed and configured correctly. All my services on ECS work with a consul agent that redirects the requests within the mesh and each service as Envoy working as proxy to communicate with the consul agent (Envoy is installed as a sidecar container for each service). The proxies are configured using the consul connect command:
consul connect envoy
My issue is when I apply a global configuration to enable access logging on my Envoy proxies, as in: https://developer.hashicorp.com/consul/docs/connect/observability/access-logs the proxies do not have logs and appear not to have the configuration enabled. Is there something I'm missing?
Versions and details:
Consul: 1.18.2
Envoy: 1.28.7
Services: ECS
Consul Leader: EC2 instance with 1 leader and 2 followers
Output of
consul config read -kind proxy-defaults -name global
:Additional information:
After writing the global configuration I checked that all the consul server instances have it correctly applied, I also restarted the services to bootstrap them from scratch. Although nothing seems to work. On the Envoy proxies, looking at
curl localhost:19000/config_dump
the access logging is not enabled for the sidecar proxies.Output sample of the Envoy config_dump:
Let me know if you need more information.
Kind Regards,
The text was updated successfully, but these errors were encountered: