# Single line files - no newline

**URL:** <https://discuss.elastic.co/t/single-line-files-no-newline/235205>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 1, 2020, 4:28pm UTC](https://discuss.elastic.co/t/single-line-files-no-newline/235205 "2020-06-01T16:28:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sjsadowski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sjsadowski/32/69513_2.png) [@sjsadowski](https://discuss.elastic.co/u/sjsadowski)\
**Post date:** [June 1, 2020, 4:28pm UTC](https://discuss.elastic.co/t/single-line-files-no-newline/235205/1 "2020-06-01T16:28:45Z")

</div>

I have a single line logfile with no newline character that is not being shipped.

I am aware that this is problematic from both searches here on the forums and some trial and error. With that being said, I don't have the option to change this behavior at the moment so I expect to continue to have single line logs with no newline character.

I've tried **close\_eof: true** and setting **close\_timeout: 1s** , but the issue is not the harvesting of the files - it's that filebeat does not ship the log until a newline is found. Aside from running a sed job on every file that lands and inserting a newline (current solution), is there a way to force filebeat to read to the end of the file and then consider the log complete and ship it?

**Edit:** this is using the 7.7.0 release of filebeat, but it happens with older releases as well.

---

<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 29, 2020, 6:28pm UTC](https://discuss.elastic.co/t/single-line-files-no-newline/235205/2 "2020-06-29T18:28:46Z")

</div>

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