# Using the multiline codec with input pipeline

**URL:** <https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350>\
**Category:** Logstash\
**Created:** [May 19, 2020, 2:58pm UTC](https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350 "2020-05-19T14:58:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Offer\_Baruch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/offer_baruch/32/68645_2.png) [@Offer\_Baruch](https://discuss.elastic.co/u/Offer_Baruch)\
**Post date:** [May 19, 2020, 2:58pm UTC](https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350/1 "2020-05-19T14:58:45Z")

</div>

Hello everyone,

I am using pipeline communication to have a different pipeline to parse different file types as input.  
My main input pipeline recognizes the file type and passes control to the correct pipeline.

I am trying to use the input pipeline with a multiline codec without much success.  
If I am using stdin input with the codec everything works fine.  
It looks like the codec statement is simply ignored when specified in the pipeline input.  
My input looks like this:

> ```
> input {
> pipeline {
> address => "my-address"
> codec => multiline {
> pattern => "^1"
> negate => true
> what => "previous"
> }
> }
> }
> 
> ```

I can't find any documentation about the pipeline input/output plugins other than example of how to use them for communicating between pipelines and I an not even sure the codec parameter is expected there.

Would appreciate your help.

---

<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 19, 2020, 3:30pm UTC](https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350/2 "2020-05-19T15:30:16Z")

</div>

The codec option on a pipeline is [ignored](https://github.com/elastic/logstash/issues/11426), by design. And yes, ignoring it silently is a bad design.

---

<div class="post-metadata">

**Author:** ![Offer\_Baruch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/offer_baruch/32/68645_2.png) [@Offer\_Baruch](https://discuss.elastic.co/u/Offer_Baruch)\
**Post date:** [May 20, 2020, 6:04am UTC](https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350/3 "2020-05-20T06:04:33Z")

</div>

Thank you for that.  
Can you think of any another way I can use multiline in such a scenario or must I use a different input with a codec to handle multiline?

thanks again  
Offer

---

<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 20, 2020, 4:01pm UTC](https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350/4 "2020-05-20T16:01:44Z")

</div>

You would have to use a different input.

---

<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 17, 2020, 4:02pm UTC](https://discuss.elastic.co/t/using-the-multiline-codec-with-input-pipeline/233350/5 "2020-06-17T16:02:04Z")

</div>

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