# Using modules alongside "normal" log processing

**URL:** <https://discuss.elastic.co/t/using-modules-alongside-normal-log-processing/210458>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 4, 2019, 5:43am UTC](https://discuss.elastic.co/t/using-modules-alongside-normal-log-processing/210458 "2019-12-04T05:43:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [December 4, 2019, 5:45pm UTC](https://discuss.elastic.co/t/using-modules-alongside-normal-log-processing/210458/2 "2019-12-04T17:45:53Z")

</div>

I can answer part of this maybe. Module source file names/paths have defaults, in this case in /usr/share/filebeat/module/haproxy/log/manifest.yml.

Modules are designed to work with Elasticsearch ingest and it's easier to go with that if you can. If you want to go thru logstash, you need to convert the ingest pipelines to logstash, see [this](https://www.elastic.co/guide/en/logstash/current/ingest-converter.html). However, some things don't convert and must be hand coded or use features that aren't available in Logstash.

I think you would want to exclude the haproxy logs from the general section, at least per [this post](https://discuss.elastic.co/t/harvesting-same-file-with-different-prospector-config/89546), it seems like it could cause problems.

Good luck 🙂

---

_[View the full topic](https://discuss.elastic.co/t/using-modules-alongside-normal-log-processing/210458)._