Can you describe how to enable the Load Balancer container to log its routing/proxying actions
@gesrat syslog is disabled by default on rancher/agent-instance instance for performance reasons. We are aware that its a limitation for haproxy logging, and its in plans to be resolved. Here is the bug to keep track of the issue:
Is there some way to enable syslog manually inside the container in the meantime? Every time I try to use the balancer I end up with intermittent issues (504, 503) and there is no way to debug what is going on without some sort of logging or stats. It is a major detriment to the load balancer IMHO.