You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HTTP and TCP/UDP don't have same command operators, REQ and RESP operators only in HTTP is important for observability. If operators only in HTTP is configured for TCP/UDP, - will be placed in related access log operator.
If user wants to deploy HTTP and TCP/UDP listeners under same GatewayClass with mergeGateways enabled, user can't attach EnvoyProxy to Gateway to let different Gateway use their own access log format, then TCP/UDP will have massive - in access log, it's unnecessary overhead and produce useless info to access log.
As a workaround, user can choose to split HTTP and TCP/UDP to different GatewayClass with their own necessary access log format.
Maybe we can consider allow user to configure access log format for HTTP and TCP/UDP separately in EnvoyProxy.
It's not critical issue indeed and will not cause any problems in envoy, all it affects is in the end Loki maybe store massive - char because TCP/UDP listener don't support HTTP-only operator, especially REQ and RESP.
Description:
HTTP and TCP/UDP don't have same command operators,
REQ
andRESP
operators only in HTTP is important for observability. If operators only in HTTP is configured for TCP/UDP,-
will be placed in related access log operator.If user wants to deploy HTTP and TCP/UDP listeners under same GatewayClass with
mergeGateways
enabled, user can't attach EnvoyProxy to Gateway to let different Gateway use their own access log format, then TCP/UDP will have massive-
in access log, it's unnecessary overhead and produce useless info to access log.As a workaround, user can choose to split HTTP and TCP/UDP to different GatewayClass with their own necessary access log format.
Maybe we can consider allow user to configure access log format for HTTP and TCP/UDP separately in EnvoyProxy.
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: