# Handling of Multiline Scenarios

**URL:** <https://discuss.elastic.co/t/handling-of-multiline-scenarios/339069>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [July 24, 2023, 10:06am UTC](https://discuss.elastic.co/t/handling-of-multiline-scenarios/339069 "2023-07-24T10:06:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [July 24, 2023, 10:06am UTC](https://discuss.elastic.co/t/handling-of-multiline-scenarios/339069/1 "2023-07-24T10:06:53Z")

</div>

Hi,  
We have a need to add a second multiline block to our filebeat config. What isn't clear to me is the order in which multiline blocks are executed. Am I right to assume that they're executed in the order that the config file is written?

Thx  
D

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [August 1, 2023, 9:32am UTC](https://discuss.elastic.co/t/handling-of-multiline-scenarios/339069/2 "2023-08-01T09:32:42Z")

</div>

Hey @dawiro,

This is interesting, I have never used multiple multiline blocks for the same input. Could you share your multiline configuration?

I guess you are using the `filestream` input, right? In that case the [parsers](https://www.elastic.co/guide/en/beats/filebeat/8.9/filebeat-input-filestream.html#_parsers) are executed from top to bottom. The `log` input doesn't support multiple multiline blocks.

---

<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:** [August 29, 2023, 11:32am UTC](https://discuss.elastic.co/t/handling-of-multiline-scenarios/339069/3 "2023-08-29T11:32:44Z")

</div>

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