On Tue, Mar 09, 2010 at 06:16:07PM -0800, Praveen Patnala wrote:
> HI Willy,
>
> I had a question on the debug mode. I got the syslogd working (using -r
> options) and we do get the logs on a different location than
> /var/log/messages by modifying the various syslog config files. This is a
> bit of a problem for us to automate launching of a machine in our
> environment since we need to edit syslog config files. If we run the haproxy
> in the debug mode and redirect the logs, do you recommend that?
Huh, not at all ! Debug mode dumps *all headers*, which is very verbose.
It will also not include important information such as IP addresses, timers,
flags, etc... As its name implies, debug mode is for debugging.
> Can you
> share any information in terms of performance slowdown or stability in this
> mode in a production environment?
It will be very expensive in terms of CPU and storage, and useless for
logging. Some people do that on development machines to get full captures
of requests and responses, but that's on development machines only.
What I really recommend you to do is to install syslog-ng with just
one instance dedicated to local UDP logging. It is very fast, will
not interfere at all with existing syslog and will not require any
system config change.
I regularly recommend this basic configuration :
> options {
> sync (0);
> time_reopen (10);
> log_fifo_size (10000);
> long_hostnames (off);
> use_dns (no);
> use_fqdn (no);
> create_dirs (no);
> keep_hostname (yes);
> };
>
> source s_udp { udp(ip(127.0.0.1) port(514)); };
>
> destination d_haproxy { file("/var/log/haproxy"); };
> filter f_local0 { facility(local0); };
> log { source(s_udp); filter(f_local0); destination(d_haproxy); };
You can even start it on a non-privileged port, or have one instance
per haproxy instance, etc... It's the easiest solution to deploy and
probably the cleanest.
Regards,
Willy
