# Pipeline to pipeline communication

**URL:** <https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541>\
**Category:** Logstash\
**Created:** [May 14, 2020, 3:56am UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541 "2020-05-14T03:56:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)\
**Post date:** [May 14, 2020, 3:56am UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541/1 "2020-05-14T03:56:39Z")

</div>

HI, I got about 15 pipelines, getting data from a DB, and I was thinking to point all those pipelines to another pipeline that will filter and index the data and various questions arise in my mind:

1-Will this create a performance issue (bottleneck)?  
2-the pipelines in pipelines.yml are executed in parallel or in order?  
3-if they are in order, then it matters where I put my filter pipeline, must be placed after my other pipelines?

```auto
- pipeline.id: db_one
  path.config: "/etc/logstash/conf.d/database/db_one.conf"
- pipeline.id: db_two
  path.config: "/etc/logstash/conf.d/database/db_two.conf"
  ....
- pipeline.id: db_fifteen
  path.config: "/etc/logstash/conf.d/database/db_fifteen.conf"
- pipeline.id: dbfilter
  path.config: "/etc/logstash/conf.d/database/filter.conf"

```

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 14, 2020, 3:12pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541/2 "2020-05-14T15:12:52Z")

</div>

> [@ElasticLiver](#):
>
> 2-the pipelines in pipelines.yml are executed in parallel or in order?

The pipelines execute in parallel.

---

<div class="post-metadata">

**Author:** ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)\
**Post date:** [May 14, 2020, 3:19pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541/3 "2020-05-14T15:19:05Z")

</div>

Hi Badger, Then how multiples pipelines use one pipeline as a filter in pipeline to pipeline comunication? they do not "fight" for that filter pipeline?

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [May 14, 2020, 4:54pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541/4 "2020-05-14T16:54:56Z")

</div>

I do not know the details, but the [collector pattern](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html#collector-pattern) is one of the standard use cases, so I have to assume it works.

---

<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 11, 2020, 4:55pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-communication/232541/5 "2020-06-11T16:55:00Z")

</div>

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