# Filebeat close\_\* clean\_\* params are confusing. Just want to wait 90s after rotation and then give up

**URL:** <https://discuss.elastic.co/t/filebeat-close-clean-params-are-confusing-just-want-to-wait-90s-after-rotation-and-then-give-up/185485>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 12, 2019, 5:31pm UTC](https://discuss.elastic.co/t/filebeat-close-clean-params-are-confusing-just-want-to-wait-90s-after-rotation-and-then-give-up/185485 "2019-06-12T17:31:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bschaeffer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bschaeffer/32/40303_2.png) [@bschaeffer](https://discuss.elastic.co/u/bschaeffer)\
**Post date:** [June 12, 2019, 5:31pm UTC](https://discuss.elastic.co/t/filebeat-close-clean-params-are-confusing-just-want-to-wait-90s-after-rotation-and-then-give-up/185485/1 "2019-06-12T17:31:06Z")

</div>

Howdy. I really don't understand what configuration I need for the `docker` input to just have filebeat do the following:

1. tail new files (read from head)
2. wait 90s after eof
3. stop tailing file, remove from registry, pretend it never ever even ever once even ever existed for a single second.

We have a high volume of files being rotated in our GKE cluster and all i really want to is for the harvester for tail new files to the end, wait a timeout and then bail (removing from registry).

---

<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:** [July 10, 2019, 5:31pm UTC](https://discuss.elastic.co/t/filebeat-close-clean-params-are-confusing-just-want-to-wait-90s-after-rotation-and-then-give-up/185485/2 "2019-07-10T17:31:10Z")

</div>

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