# Unable to setup HAproxy monitoring using Filebeat module

**URL:** <https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 8, 2019, 7:26pm UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241 "2019-05-08T19:26:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssardana08](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ssardana08/32/54388_2.png) [@ssardana08](https://discuss.elastic.co/u/ssardana08)\
**Post date:** [May 8, 2019, 7:26pm UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241/1 "2019-05-08T19:26:00Z")

</div>

Hi all,

I'm trying to setup a good alarming and visualization on Kibana for my haproxy setup using ELK and Filebeat.

But everytime I use Filebeat in-built module for haproxy and goes to the step of setting up environment variables, it throws following error:

`instance/beat.go:802 Exiting: 1 error: error loading config file`

Need help configuring it!

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)\
**Post date:** [May 9, 2019, 12:46pm UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241/2 "2019-05-09T12:46:51Z")

</div>

does error says something more? do you provide a config path?  
maybe config is incorrectly written or has incorrect permissions

---

<div class="post-metadata">

**Author:** ![ssardana08](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ssardana08/32/54388_2.png) [@ssardana08](https://discuss.elastic.co/u/ssardana08)\
**Post date:** [May 10, 2019, 6:53am UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241/3 "2019-05-10T06:53:32Z")

</div>

Hey @Michal_Pristas,  
I passed all the steps in this doc [https://www.elastic.co/guide/en/beats/filebeat/7.0/filebeat-module-haproxy.html](https://www.elastic.co/guide/en/beats/filebeat/7.0/filebeat-module-haproxy.html)

After setting up the initial variable, I got this message:  
Loaded machine learning job configurations

Also I've made changes in haproxy.yml -\> var.paths and var.input accordingly

Started filebeat. But still I'm not able to see data on kibana.

---

<div class="post-metadata">

**Author:** ![Michal\_Pristas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_pristas/32/46639_2.png) [@Michal\_Pristas](https://discuss.elastic.co/u/Michal_Pristas)\
**Post date:** [May 10, 2019, 12:57pm UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241/4 "2019-05-10T12:57:47Z")

</div>

can you share a config? how is your output defined?  
did the previous error go away? (`instance/beat.go:802 Exiting: 1 error: error loading config file`)

---

<div class="post-metadata">

**Author:** ![ssardana08](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ssardana08/32/54388_2.png) [@ssardana08](https://discuss.elastic.co/u/ssardana08)\
**Post date:** [May 10, 2019, 1:23pm UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241/5 "2019-05-10T13:23:07Z")

</div>

Hey @Michal_Pristas.  
So the previous error went off. I initiated the entire setup from scratch and proceeded with normal setup.

So after few minutes I got all data visualized on Kibana.

Thanks for your help 🙂

---

<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:** [June 7, 2019, 1:26pm UTC](https://discuss.elastic.co/t/unable-to-setup-haproxy-monitoring-using-filebeat-module/180241/6 "2019-06-07T13:26:19Z")

</div>

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