Hi Chris,
If you have a spare nic, you can set this to a different subnet from the
other interfaces and set one on a syslog server, then in the global section
of haproxy setup the logging section, for example:
log 192.168.5.5:514 local6
Make sure your syslog-ng is set for tcp and udp on 514, then you can use
filters to split out the different logs based on receiving servers name in
the message in syslog-ng.
Joe
On Wed, Jan 11, 2012 at 7:34 PM, Chris Miller <[email protected]>wrote:
>
> We're looking to utilize access logs from HAProxy rather than from
> the backend application servers. It appears we can set logging
> directives to one syslog host per "listen" directive, this doesn't
> really help us split into separate logs per host. One thought it to
> use syslog-ng which has filters that would allow this, but at an
> unknown overhead for a high traffic load balancer. Before we
> reinvent the wheel, I just wanted to see if anyone has a recommended
> way of addressing this. I was unable to find anything on Google...
>
> Regards,
> Chris
>
> Chris Miller
> President - Rocket Scientist
> ScratchSpace Inc.
> (831) 621-7928
> http://www.scratchspace.com
>
>
>
