# Is multiline codec safe to use in TCP input?

**URL:** <https://discuss.elastic.co/t/is-multiline-codec-safe-to-use-in-tcp-input/179449>\
**Category:** Logstash\
**Created:** [May 3, 2019, 1:47am UTC](https://discuss.elastic.co/t/is-multiline-codec-safe-to-use-in-tcp-input/179449 "2019-05-03T01:47:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vbohata](https://avatars.discourse-cdn.com/v4/letter/v/a8b319/32.png) [@vbohata](https://discuss.elastic.co/u/vbohata)\
**Post date:** [May 3, 2019, 1:47am UTC](https://discuss.elastic.co/t/is-multiline-codec-safe-to-use-in-tcp-input/179449/1 "2019-05-03T01:47:16Z")

</div>

Docs warns about using the multiline codec in beats inputs etc. because of mixing up data. As tcp input already uses line codec and the events processing seems to be related/separated to each network socket it should be safe to use multiline instead of line (assuming the syslog sender does not mix the lines by itself), am I right?

---

<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:** [May 31, 2019, 1:47am UTC](https://discuss.elastic.co/t/is-multiline-codec-safe-to-use-in-tcp-input/179449/2 "2019-05-31T01:47:26Z")

</div>

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