# Haproxy module with master version

**URL:** <https://discuss.elastic.co/t/haproxy-module-with-master-version/148094>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 11, 2018, 9:01am UTC](https://discuss.elastic.co/t/haproxy-module-with-master-version/148094 "2018-09-11T09:01:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pollux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pollux/32/31600_2.png) [@pollux](https://discuss.elastic.co/u/pollux)\
**Post date:** [September 11, 2018, 9:01am UTC](https://discuss.elastic.co/t/haproxy-module-with-master-version/148094/1 "2018-09-11T09:01:29Z")

</div>

HI,

I compiled filebeat from master (go get + make) and it works. I launch filebeat with the haproxy module. The conf is:

- module: haproxy  
http:  
enabled: true  
var.input: "file"  
var.paths: ["/var/log/haproxy.log"]

The haproxy is from debian repo, v1.5.8. The only thing that I have about log in my haproxy.cfg is

```
global
   log /dev/log local0
   log /dev/log local1 notice

```

In elasticsearch I have this error:

```
Provided Grok expressions do not match field value: [Sep 11 10:43:06 pompom haproxy[666]: 8.8.8.8 - - [11/Sep/2018:08:43:06 +0000] \\\"GET / HTTP/1.1\\\" 200 457 \\\\\\\"\\\\\\\" \\\\\\\"\\\\\\\" 42070 \\\\098 \\\"https~\\\" \\\"vm-abc\\\" \\\"vm-abc\\\" \\\\86 0 1 15 104 ---- 1 1 \\\\0 1 0 0 0 \\\"\\\" \\\"\\\" \\\\ ]

```

I know that haproxy is still alpha, do you think it worth opening an issue in github ?

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [September 11, 2018, 3:35pm UTC](https://discuss.elastic.co/t/haproxy-module-with-master-version/148094/2 "2018-09-11T15:35:12Z")

</div>

@pollux it's worth creating a new issue with your log attached.

I think our grok patterns are not general enough to support every case.

> <https://github.com/elastic/beats/blob/master/filebeat/module/haproxy/http/ingest/pipeline.json#L7-L8>

---

<div class="post-metadata">

**Author:** ![pollux](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pollux/32/31600_2.png) [@pollux](https://discuss.elastic.co/u/pollux)\
**Post date:** [September 13, 2018, 8:34am UTC](https://discuss.elastic.co/t/haproxy-module-with-master-version/148094/3 "2018-09-13T08:34:48Z")

</div>

In this case, this is the standard logs from haproxy (debian-packaged) I don't know if debian change anything to the default config (this is sad but it could).

Issue: [https://github.com/elastic/beats/issues/8301](https://github.com/elastic/beats/issues/8301)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 11, 2018, 8:34am UTC](https://discuss.elastic.co/t/haproxy-module-with-master-version/148094/4 "2018-10-11T08:34:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.