# FileBeat file is falling under ignore older

**URL:** <https://discuss.elastic.co/t/filebeat-file-is-falling-under-ignore-older/61210>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 22, 2016, 8:16am UTC](https://discuss.elastic.co/t/filebeat-file-is-falling-under-ignore-older/61210 "2016-09-22T08:16:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![il.bert](https://avatars.discourse-cdn.com/v4/letter/i/ac91a4/32.png) [@il.bert](https://discuss.elastic.co/u/il.bert)\
**Post date:** [October 10, 2016, 8:28am UTC](https://discuss.elastic.co/t/filebeat-file-is-falling-under-ignore-older/61210/4 "2016-10-10T08:28:17Z")

</div>

So you are saying logstash is not sending ack? I tried debugging the log pipeline and I see the logs in kibana.  
That's exactly why I connected the filebeat logs itself: I see that error in kibana so logs are going straight forward to the destination, not more than 10s after they are created.  
Furthermore it never happens in peak time, I usually see it during night when the pipeline is off load.

how are those ack messages sent from logstash back to filebeat? does it use a special port or something else I can check?

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-file-is-falling-under-ignore-older/61210)._