# Filebeat haproxy module

**URL:** <https://discuss.elastic.co/t/filebeat-haproxy-module/159629>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 6, 2018, 12:56am UTC](https://discuss.elastic.co/t/filebeat-haproxy-module/159629 "2018-12-06T00:56:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Mark\_Bassett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_bassett/32/45353_2.png) [@Mark\_Bassett](https://discuss.elastic.co/u/Mark_Bassett)\
**Post date:** [December 6, 2018, 7:00pm UTC](https://discuss.elastic.co/t/filebeat-haproxy-module/159629/3 "2018-12-06T19:00:08Z")

</div>

I'm wondering if this is related to

> [@Typo in syslog\_rfc3164.rl causes parsing errors for December syslog dates](https://discuss.elastic.co/t/typo-in-syslog-rfc3164-rl-causes-parsing-errors-for-december-syslog-dates/159030):
>
> For confirmed bugs, please report: Version: 6.3.2 Operating System: FreeBSD GitHub Link: [https://github.com/elastic/beats/issues/9323](https://github.com/elastic/beats/issues/9323) Steps to Reproduce: With the system clock on the computer where filebeat is installed set to the month of December, attempt to ingest a syslog message using the syslog input plugin. These are the errors I get: 2018-12-02T07:38:44.727Z ERROR [syslog] syslog/input.go:114 can't not parse event as syslog rfc3164 {"message": "Dec 02 07:38:44 freebsd-11-2 crontab[81…

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-haproxy-module/159629)._