# Filebeat do not see file updates after a while

**URL:** https://discuss.elastic.co/t/filebeat-do-not-see-file-updates-after-a-while/34914
**Category:** Beats
**Tags:** filebeat
**Created:** [November 18, 2015, 10:08am UTC](https://discuss.elastic.co/t/filebeat-do-not-see-file-updates-after-a-while/34914 "2015-11-18T10:08:52Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [November 23, 2015, 4:30pm UTC](https://discuss.elastic.co/t/filebeat-do-not-see-file-updates-after-a-while/34914/23 "2015-11-23T16:30:08Z")

</div>

@ogauchard Yes, the problem is that the next change is detected but the file pointer is potentially set to the end. Currently ignore\_older mixes two different functionalities into one: [https://github.com/elastic/filebeat/issues/181](https://github.com/elastic/filebeat/issues/181) Feel free to also comment here what your expectations would be.

We still have to think again through the different use cases etc. and what should happen in which case, but at the moment the best potential solution is to set ignore\_older to a much higher value.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-do-not-see-file-updates-after-a-while/34914)._