# Pipeline-to-Pipeline in 6.2.4

**URL:** <https://discuss.elastic.co/t/pipeline-to-pipeline-in-6-2-4/159057>\
**Category:** Logstash\
**Created:** [December 2, 2018, 8:55pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-in-6-2-4/159057 "2018-12-02T20:55:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarmendeos](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@tarmendeos](https://discuss.elastic.co/u/tarmendeos)\
**Post date:** [December 2, 2018, 8:55pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-in-6-2-4/159057/1 "2018-12-02T20:55:31Z")

</div>

Hello! I'm relatively new to the ELK stack, and I've got a problem where I am in need of the output-isolator pattern described in [https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html), but the feature has just been released on 6.5 and I am still on 6.2.4.

Is there a viable workaround without upgrading to 6.5 at the moment? Is it possible to say, use the file-output plugin and multiple pipelines to duplicate the pipeline-to-pipeline?

For example,

# config/pipelines.yml

- pipeline.id: intake  
queue.type: persisted  
config.string: |  
input { beats { port =\> 5044 } }  
output { file { path =\> file1 } file { path =\> file2 } }
- pipeline.id: buffered-es  
queue.type: persisted  
config.string: |  
input { file { path =\> file1} }  
output { elasticsearch { } }
- pipeline.id: buffered-http  
queue.type: persisted  
config.string: |  
input { file { path =\> file2} }  
output { http { } }

Thanks in advance!

---

<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:** [December 30, 2018, 8:55pm UTC](https://discuss.elastic.co/t/pipeline-to-pipeline-in-6-2-4/159057/2 "2018-12-30T20:55:37Z")

</div>

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