# Multiple line with extreme long log "line"

**URL:** <https://discuss.elastic.co/t/multiple-line-with-extreme-long-log-line/23806>\
**Category:** Logstash\
**Created:** [June 17, 2015, 6:43am UTC](https://discuss.elastic.co/t/multiple-line-with-extreme-long-log-line/23806 "2015-06-17T06:43:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![loc](https://avatars.discourse-cdn.com/v4/letter/l/e8c25b/32.png) [@loc](https://discuss.elastic.co/u/loc)\
**Post date:** [June 17, 2015, 6:43am UTC](https://discuss.elastic.co/t/multiple-line-with-extreme-long-log-line/23806/1 "2015-06-17T06:43:54Z")

</div>

I am using multiple-line in my logstash. Logstash is receiving log from logstash-forwarder. It works fine. However, when there is extreme long multiple line log (some dump information), logstash stop processing. I can imagine that it should be ok if I can define maximum number of lines. However, there is no such option. Any one meet the same issue and any solution?

Thanks  
Loc

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [June 17, 2015, 7:03am UTC](https://discuss.elastic.co/t/multiple-line-with-extreme-long-log-line/23806/2 "2015-06-17T07:03:08Z")

</div>

Are you using the Codec Multiline or are you using the filter. I use the filter and it tends to get over run. From my understanding the multiline codec for file input is better. I have yet to check it out.

The only solution for this that I can think of is to increase your heap space if the codec does not help

---

<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:** [July 6, 2017, 5:37am UTC](https://discuss.elastic.co/t/multiple-line-with-extreme-long-log-line/23806/3 "2017-07-06T05:37:14Z")

</div>


