Hi Damien
I may be wrong, but as far as I can gather the 1024-byte limitation is imposed by the syslog protocol RFC (http://www.faqs.org/rfcs/rfc3164.html) and not HAproxy itself.
Regards,
Graeme.
On 8 September 2011 16:09, Damien Hardy <damienhardy.bal#gmail.com> wrote:
> Hello there.
>
> We are working on our realtime statistics of consultation platform based on
> haproxy logs.
> Our probleme is that logs can capture HTTP headers but are limited to a
> 1024 length string witch is very short if Host: Referer: and User-Agent: are
> captured as we are doing.
>
> Is it planned to set the max log size by config parameter.
>
> Do you now if there is any side effects increasing this value and rebuild a
> package ?
> The syslog server is a cloudera flume node located on the same server with
> haproxy (flume is not able to read in a Unix socket as far as I know).
>
> Thank you.
>
> Best regards,
>
> --
> Damien
>
>
>
Received on 2011/09/08 16:15
This archive was generated by hypermail 2.2.0 : 2011/09/08 16:30 CEST