Internal listener access logging in Envoy about istio HOT 5 OPEN

I recall istio only print listener access log when 404 in the past?

from istio.

This isn't about listener access logs, but for hbone the destination endpoint is an internal listener instead of ip

from istio.

you can either change the hardcode log format or just remove it(this option may cause difficult to debug).

from istio.

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)

from istio.

There are two parts here:

• Source ip is envoy://internal_client_address/. This I think requires us to either change envoy core, or pass "real source ip" as metadata across the internal listener
• Destination IP is "envoy://connect_originate/10.244.0.10:80". This seems easier, since the original IP is known to be in EDS metadata and access logs can access it. However, we would want to do something like metadata.ip OR upstream_addr for the non HBONE cases; I don't see how to do that in envoy. %CEL(...) seemed promising but has a lot of bugs

from istio.