# Filebeat haproxy module - with custom log\_format - how could it ever work? **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [July 20, 2022, 7:56pm UTC](https://discuss.elastic.co/t/filebeat-haproxy-module-with-custom-log-format-how-could-it-ever-work/310199 "2022-07-20T19:56:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jrwren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jrwren/32/108596_2.png) [@jrwren](https://discuss.elastic.co/u/jrwren)\ **Post date:** [July 20, 2022, 7:56pm UTC](https://discuss.elastic.co/t/filebeat-haproxy-module-with-custom-log-format-how-could-it-ever-work/310199/1 "2022-07-20T19:56:07Z")
It isn't clear from the docs here [HAproxy module | Filebeat Reference [master] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-module-haproxy.html) How the logs are parsed. If I have customized the haproxy logs using a `log-format ` directive in my haproxy.conf, how can filebeat possibly parse the log without configuration to match my custom `log-format`? How can I configure this? I see **[Extend filebeat logstash patterns for the haproxy modul · Issue #21332 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/21332)** is kind of similar. Is it possible at all? My log-format is %{+Q}o\ %{-Q}ci\ -\ -\ [%trg]\ %r\ %ST\ %B\ %cp\ %ms\ %ft\ %b\ %s\ %TR\ %Tw\ %Tc\ %Tr\ %Tt\ %tsc\ %ac\ %fc\ %bc\ %sc\ %rc\ %sq\ %bq\ %CC\ %CS\ %hrl\ %hsl\ %sslv\ I'd like to add more captures and possibly more %T timings. How could filebeat haproxy module support this at all? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 17, 2022, 9:56pm UTC](https://discuss.elastic.co/t/filebeat-haproxy-module-with-custom-log-format-how-could-it-ever-work/310199/2 "2022-08-17T21:56:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.