# Hello elastic - Multiple Pipelines

**URL:** https://discuss.elastic.co/t/hello-elastic-multiple-pipelines/298484
**Category:** Elasticsearch
**Tags:** docker, ingest-pipeline
**Created:** [March 1, 2022, 9:04am UTC](https://discuss.elastic.co/t/hello-elastic-multiple-pipelines/298484 "2022-03-01T09:04:20Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [March 1, 2022, 2:34pm UTC](https://discuss.elastic.co/t/hello-elastic-multiple-pipelines/298484/5 "2022-03-01T14:34:16Z")

</div>

No only a single pipeline per input type.

Here are some thoughts on a solution.

> [@How to configure multiple ingest pipelines on filebeat to load data in elastic cloud](https://discuss.elastic.co/t/how-to-configure-multiple-ingest-pipelines-on-filebeat-to-load-data-in-elastic-cloud/270290/4):
>
> [Here](https://discuss.elastic.co/t/setting-multiple-pipelines-for-elasticserach-output/269999/2) is a method / suggestion The advantage of doing it this way having a top level common pipeline that then directs and sorts to the correct specific pipeline is that you can control this outside of beat so if you change something you don't need to change the beats config. You can also build modular pipelines so they can be reused. You can also define a pipeline per input ... See [here](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-log.html#_pipeline_11)...

---

_[View the full topic](https://discuss.elastic.co/t/hello-elastic-multiple-pipelines/298484)._