Ask questionsIncrease support of log formats in haproxy filebeat module
During the investigation of #8301 issue we identified some patterns that could be added to the initial module implemented for haproxy (#8014):
option tcplog. #8526 #8637
Feb 6 12:12:56 localhost haproxy: 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
Feb 6 12:12:09 localhost haproxy: Connect from 10.0.1.2:33312 to 10.0.3.31:8012 (www/HTTP)
Sep 13 15:51:16 debian8-haproxy haproxy: Server mysvc/myserver01 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
Sep 13 15:51:15 debian8-haproxy haproxy: backend myservers has no server available!
haproxy.mode. Right now, only HAProxy default format outputs a
modefield pointing if the log line is either HTTP or TCP. But the HTTP and TCP logs doesn't actually show anything like this.
Answer questions andrask
#13995 was closed automatically but it has not been fixed, I believe.