# Filebeat audit module and close\_timeout

**URL:** <https://discuss.elastic.co/t/filebeat-audit-module-and-close-timeout/150560>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 1, 2018, 11:17am UTC](https://discuss.elastic.co/t/filebeat-audit-module-and-close-timeout/150560 "2018-10-01T11:17:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikkop71](https://avatars.discourse-cdn.com/v4/letter/m/bcef8e/32.png) [@mikkop71](https://discuss.elastic.co/u/mikkop71)\
**Post date:** [October 1, 2018, 11:17am UTC](https://discuss.elastic.co/t/filebeat-audit-module-and-close-timeout/150560/1 "2018-10-01T11:17:47Z")

</div>

Version: 5.4.1

We have a problem that Filebeat keeps audit log file locked after log rotation.  
Restarting Filebeat is workaround to the issue.

Question is can we use close\_timeout with this module or is there some equivalent system?

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [October 1, 2018, 11:30am UTC](https://discuss.elastic.co/t/filebeat-audit-module-and-close-timeout/150560/2 "2018-10-01T11:30:32Z")

</div>

`close_*` options are effective in case of modules, not only inputs. `close_timeout` would be a good choice to close files after log rotation.

Example configuration:

```auto
filebeat.modules
- module: auditd
  log:
    enabled: true
    prospector:
      close_timeout: 5m

```

---

<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 29, 2018, 11:30am UTC](https://discuss.elastic.co/t/filebeat-audit-module-and-close-timeout/150560/3 "2018-10-29T11:30:36Z")

</div>

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