-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Internal listener access logging in Envoy #50321
Comments
I recall istio only print listener access log when 404 in the past? |
This isn't about listener access logs, but for hbone the destination endpoint is an internal listener instead of ip |
you can either change the hardcode log format or just remove it(this option may cause difficult to debug). |
I think we want to log the real source and dest IP. This may just be changing the format to access some other info, but we might need to make changes in Envoy/istio-proxy to expose that info if its not available (not sure what info we have) |
There are two parts here:
|
|
When we use HBONE in envoy, we get access logs showing unexpected info
Without hbone:
With hbone:
Probably we can tweak these to avoid exposing internals
The text was updated successfully, but these errors were encountered: