1

i'm trying to configure my HAProxy to log more information than just saying "proxy backend_xx started" and it looks like i am failing to understand how it works.

my HAProxy is a pure TCP LB (just forwards requests from the frontend to backends, pure L4).

i would like to have logs as mentionned in the HAProxy documentation here https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#8.2.2

here is my configuration & issues at the moment, in the "global/default sections", i have :

#--------------------------------------------------------------------- # Global settings #--------------------------------------------------------------------- global daemon user haproxy group haproxy log /dev/log local6 debug maxconn 50000 chroot /var/lib/haproxy pidfile /var/run/haproxy.pid #--------------------------------------------------------------------- # common defaults that all the 'listen' and 'backend' sections will # use if not designated in their block #--------------------------------------------------------------------- defaults mode tcp option tcplog log global option dontlognull timeout connect 5000 timeout client 50000 timeout server 50000 

i also have this option under my frontend :

frontend main_https_listen bind xxxxxxxxxxxxxx:443 mode tcp option tcplog xxxxxxx 

i configured a file in my rsyslog.d with :

[root@xxxxxxx ~]# cat /etc/rsyslog.d/haproxy.conf # ----------------------------------------------- # Haproxy specific logging configuration # ----------------------------------------------- local6.debug /var/log/haproxy-traffic.log local6.notice /var/log/haproxy-admin.log [root@xxxxxxx ~]# 

unfortunately, both files contain the same information, e.g:

[root@xxxxxxx ~]# tail -11 /var/log/haproxy-admin.log Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy stats started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy main_https_listen started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT35073 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT34305 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT28548 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT28756 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT36702 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_UAT_AT28546 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_PRD_AT28547 started. [root@xxxxxxx ~]# tail -11 /var/log/haproxy-traffic.log Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy stats started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy main_https_listen started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT35073 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT34305 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT28548 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT28756 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_SIT_AT36702 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_UAT_AT28546 started. Feb 25 18:05:30 xxxxxxx haproxy[838761]: Proxy backend_PRD_AT28547 started. 

while i would expect having the traffic log to generate things like in the documentation, e.g:

Feb 6 12:12:56 localhost \ haproxy[14387]: 10.0.1.2:33313 [06/Feb/2009:12:12:51.443] fnt \ bck/srv1 0/0/5007 212 -- 0/0/0/0/3 0/0 

any idea on what is wrong in my configuration ?

thanks again

regards

1 Answer 1

1

i found the issue. i had to add a "log global" under the "frontend" block to tell the frontend to log there:

frontend main_https_listen bind xxxxxx:443 mode tcp option tcplog log global 

as simple as that. i can see the logs now, e.g:

Feb 27 18:05:20 xxxxx haproxy[1392050]: xxxxx:61767 [27/Feb/2020:18:05:14.532] main_https_listen backend_PRD_AT28779/server_PRD_AT28779_1 3/1/6315 4031 -- 0/0/0/0/0 0/0 Feb 27 18:05:20 xxxxx haproxy[1392050]: xxxxx:61767 [27/Feb/2020:18:05:14.532] main_https_listen backend_PRD_AT28779/server_PRD_AT28779_1 3/1/6315 4031 -- 0/0/0/0/0 0/0 

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.