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
We leverage JSON logs to kick out structured values via haproxy -> rsyslog -> LOGGING_INFRA. Recently we noticed haproxy truncating some log-entries.
Could we expose a configmap entry akin to syslog-endpoint and syslog-format to manage syslog-length, which would default to the standard default of 1024, but allow users to specify longer lines if required?
Current (GROSS) work-around: specify syslog-endpoint as 127.0.0.1:514 len 2048 to shim the magic haproxy value in.
We leverage JSON logs to kick out structured values via haproxy -> rsyslog -> LOGGING_INFRA. Recently we noticed haproxy truncating some log-entries.
Could we expose a configmap entry akin to
syslog-endpoint
andsyslog-format
to managesyslog-length
, which would default to the standard default of 1024, but allow users to specify longer lines if required?Current (GROSS) work-around: specify
syslog-endpoint
as127.0.0.1:514 len 2048
to shim the magic haproxy value in.Upstream docs: https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#3.1-log
The text was updated successfully, but these errors were encountered: