# Logstash 6 - Multiple Pipelines for One Input

**URL:** <https://discuss.elastic.co/t/logstash-6-multiple-pipelines-for-one-input/107929>\
**Category:** Logstash\
**Created:** [November 16, 2017, 12:05pm UTC](https://discuss.elastic.co/t/logstash-6-multiple-pipelines-for-one-input/107929 "2017-11-16T12:05:06Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\
**Post date:** [November 17, 2017, 2:13pm UTC](https://discuss.elastic.co/t/logstash-6-multiple-pipelines-for-one-input/107929/7 "2017-11-17T14:13:21Z")

</div>

You would run multiple instances of filebeat with different configs (paths and logstash host:port).

> [@Multiple Filebeat instance](https://discuss.elastic.co/t/multiple-filebeat-instance/71904):
>
> I am using Filebeat 5.1 on Centos Linux and have following constraints =\> need to run multiple Filebeat instances on same hosts. Each instance shall work with its own config yml. Start and stop individual Filebeat instances without affecting other instances. Can anybody provide more details how to achieve any of the above requirements ? Also, it will be helpful to know whether there is any API by which I can start/stop Filebeat. Using /etc/init.d/filebeat restart command somewhat not real…

---

_[View the full topic](https://discuss.elastic.co/t/logstash-6-multiple-pipelines-for-one-input/107929)._