# Filebeats - skips lines

**URL:** <https://discuss.elastic.co/t/filebeats-skips-lines/103018>\
**Category:** Beats\
**Created:** [October 6, 2017, 1:36pm UTC](https://discuss.elastic.co/t/filebeats-skips-lines/103018 "2017-10-06T13:36:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![adachi](https://avatars.discourse-cdn.com/v4/letter/a/85f322/32.png) [@adachi](https://discuss.elastic.co/u/adachi)\
**Post date:** [October 6, 2017, 1:36pm UTC](https://discuss.elastic.co/t/filebeats-skips-lines/103018/1 "2017-10-06T13:36:24Z")

</div>

I've got a log file which has 200 empty lines in the end (pre-write to allocate space).  
When the software writes to this file it replaces empty lines with logs and adds more empty lines in the end when 200 lines have been used.  
Due to this behavior Filebeats skips some lines.  
Is there a way for Filebeats to recognize pre-allocation and process all lines? (for example: stop processing before empty line?)

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [October 8, 2017, 10:44am UTC](https://discuss.elastic.co/t/filebeats-skips-lines/103018/2 "2017-10-08T10:44:45Z")

</div>

Filebeat tails log files. It remembers the last read lines. Your way of updating the log files relies on some weird non-standard behavior/protocol.

---

<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:** [October 27, 2017, 1:36pm UTC](https://discuss.elastic.co/t/filebeats-skips-lines/103018/3 "2017-10-27T13:36:32Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.