# Split pipeline, multiple pipiline filter in logstash management center

**URL:** https://discuss.elastic.co/t/split-pipeline-multiple-pipiline-filter-in-logstash-management-center/196297
**Category:** Logstash
**Created:** [August 22, 2019, 10:31am UTC](https://discuss.elastic.co/t/split-pipeline-multiple-pipiline-filter-in-logstash-management-center/196297 "2019-08-22T10:31:01Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)
#### Post date: [August 22, 2019, 10:31am UTC](https://discuss.elastic.co/t/split-pipeline-multiple-pipiline-filter-in-logstash-management-center/196297/1 "2019-08-22T10:31:01Z")

</div>

As we as knew, with logstash pipeline, we can use multiple pipeline for multiple filter logstash on event and logstash will be execute pipeline order by naming of pipline  
For example :

- 001-input-beat.conf
- 002-input-winevent.conf
- 100-filter-beat-1.conf
- 101-filter-beat-2.conf
- 120-filter-winevent-1.conf
- 121-filter-winevent-2.conf
- 122-filter-winevent-3.conf
- 123-filter-winevent-2.conf
- 900-output-beat.conf
- 900-output-winevent.conf

So in Elastic Stack 7.X version, have feature manager pippeline on Kibana (store config pipeline in ES). That is awesome feature. But i have some question :  
How to make multiple filter for one pipeline  
I have some pipeline in Pipeline center management :  
Pipie-winevent  
Pipie-beat  
Pipie-nginx

Here is content of **ls-winevent-pipeline**

```
input {}
filter { 
  ## contain 120-filter-winevent-1.conf
  ## contain 121-filter-winevent-2.conf
  ## contain 122-filter-winevent-3.conf
  ## contain 123-filter-winevent-4.conf
}
output {}

```

Have problem, pipeline have very long content. How to split filter to other filter pipeline that does not affeect the other pipline

---

<div class="post-metadata">

### Author: ![admlko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/admlko/32/21787_2.png) [@admlko](https://discuss.elastic.co/u/admlko)
#### Post date: [August 23, 2019, 5:39am UTC](https://discuss.elastic.co/t/split-pipeline-multiple-pipiline-filter-in-logstash-management-center/196297/2 "2019-08-23T05:39:17Z")

</div>

I don't think this is currently possible (at least not stable solution).  
I have been waiting for the [pipeline-to-pipeline communication](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html) to reach GA status in order to convert my pipelines for that. Then I could achieve what you are also trying to do.  
So every filter (which forms sensible workload in order to be a pipeline) would be a separate pipeline and the filter pipelines would take input and push output into virtual addresses (other pipelines).

---

<div class="post-metadata">

### Author: ![tatdat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tatdat/32/113160_2.png) [@tatdat](https://discuss.elastic.co/u/tatdat)
#### Post date: [August 28, 2019, 3:08am UTC](https://discuss.elastic.co/t/split-pipeline-multiple-pipiline-filter-in-logstash-management-center/196297/3 "2019-08-28T03:08:21Z")

</div>

Yeah, thank you so much, That's all i need. Hope in 7.4 version, Elastic team release GA 😃

---

<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: [September 25, 2019, 3:08am UTC](https://discuss.elastic.co/t/split-pipeline-multiple-pipiline-filter-in-logstash-management-center/196297/4 "2019-09-25T03:08:21Z")

</div>

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