# Logstash input file codec multiline not working as expected

**URL:** https://discuss.elastic.co/t/logstash-input-file-codec-multiline-not-working-as-expected/55913
**Category:** Logstash
**Created:** [July 19, 2016, 6:29pm UTC](https://discuss.elastic.co/t/logstash-input-file-codec-multiline-not-working-as-expected/55913 "2016-07-19T18:29:58Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![sumitkgaur](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@sumitkgaur](https://discuss.elastic.co/u/sumitkgaur)
#### Post date: [September 13, 2016, 6:13am UTC](https://discuss.elastic.co/t/logstash-input-file-codec-multiline-not-working-as-expected/55913/3 "2016-09-13T06:13:04Z")

</div>

Please go through the link below discuss the same problem

> [@Logstash Does Not Read In Last Line of Log](https://discuss.elastic.co/t/logstash-does-not-read-in-last-line-of-log/2706/14):
>
> Multiline filter has been deprecated in favor of multiline-codec But the problem still persist with codec . Does anybody has any workaround ? Last line of the logs is not getting processed input { beats { port =\> 5044 codec =\> multiline { pattern =\> "^\s" negate =\> "true" what =\> "previous" } } }

It is a long existing problem. As a workaround people used to use multiline filter and logs were getting parsed corrcetly. BUT now Multiline filter has been deprecated in favor of multiline-codec  
Does anybody has any other workaround ? Last line of the logs is still not getting processed.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-input-file-codec-multiline-not-working-as-expected/55913)._