On Wed, Aug 26, 2020 at 06:31:21PM +0300, Ciprian Dorin Craciun wrote: > On Wed, Aug 26, 2020 at 6:29 PM Willy Tarreau <[email protected]> wrote: > > > Then, still related to logging, might I add a feature request to just > > > use "raw" lines over UDP or TCP, instead of SysLog? (Just as we have > > > now support for `stdout`, but with network support.) > > > > You already have it. I'm doing this: > > > > log 127.0.0.1:5514 format raw daemon > > log-format "%[uuid]" > > > > And netcat shows me only the uuid with no header nor anything. So > > technically speaking I don't think you're missing anything for this. > > > This is nice. I'll have to give it a try. (I thought that the `raw` > applied only to `stdout`.
I think it used to be the case for quite some time, probably that it's become available with 2.2 and the rework needed for TCP servers. > However we are missing the TCP support. :) You have it in 2.2. You need to declare a ring buffer, which itself is chained to the TCP log server. Ah I've just found you an example here: https://www.haproxy.com/blog/announcing-haproxy-2-2/#syslog-over-tcp And in 2.3 we're even starting to receive syslog to forward and load balance it (including with format conversion and UDP->TCP). Cheers, Willy
