# Load Balancer debugging - how to enable syslog logging

**URL:** <https://forums.suse.com/t/load-balancer-debugging-how-to-enable-syslog-logging/1137>\
**Category:** Rancher 1.x\
**Created:** [December 1, 2015, 6:26pm UTC](https://forums.suse.com/t/load-balancer-debugging-how-to-enable-syslog-logging/1137 "2015-12-01T18:26:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gesrat](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/gesrat/32/699_2.png) [@gesrat](https://forums.suse.com/u/gesrat)\
**Post date:** [December 1, 2015, 6:26pm UTC](https://forums.suse.com/t/load-balancer-debugging-how-to-enable-syslog-logging/1137/1 "2015-12-01T18:26:12Z")

</div>

Can you describe how to enable the Load Balancer container to log its routing/proxying actions

---

<div class="post-metadata">

**Author:** ![alena](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/alena/32/50_2.png) [@alena](https://forums.suse.com/u/alena)\
**Post date:** [December 1, 2015, 6:56pm UTC](https://forums.suse.com/t/load-balancer-debugging-how-to-enable-syslog-logging/1137/2 "2015-12-01T18:56:23Z")

</div>

@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:

> <https://github.com/rancher/rancher/issues/2268>
>
> Can we make the default healthcheck haproxy config log failed checks? (and then expose where those checks are running so you...

---

<div class="post-metadata">

**Author:** ![andyshinn](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/andyshinn/32/442_2.png) [@andyshinn](https://forums.suse.com/u/andyshinn)\
**Post date:** [May 24, 2016, 5:14pm UTC](https://forums.suse.com/t/load-balancer-debugging-how-to-enable-syslog-logging/1137/3 "2016-05-24T17:14:14Z")

</div>

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.