# Can you configure filebeat to exit as soon as eof is reached?

**URL:** <https://discuss.elastic.co/t/can-you-configure-filebeat-to-exit-as-soon-as-eof-is-reached/57867>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 11, 2016, 11:01pm UTC](https://discuss.elastic.co/t/can-you-configure-filebeat-to-exit-as-soon-as-eof-is-reached/57867 "2016-08-11T23:01:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![lin-zhao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lin-zhao/32/11147_2.png) [@lin-zhao](https://discuss.elastic.co/u/lin-zhao)\
**Post date:** [August 11, 2016, 11:01pm UTC](https://discuss.elastic.co/t/can-you-configure-filebeat-to-exit-as-soon-as-eof-is-reached/57867/1 "2016-08-11T23:01:29Z")

</div>

I'm trying to do benchmark on filebeat and elasticsearch and would like to time the time taken to publish and index a file. Closest configuration I can find is close\_eof, but it doesn't cause filebeat process to exit.

---

<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:** [August 12, 2016, 8:01am UTC](https://discuss.elastic.co/t/can-you-configure-filebeat-to-exit-as-soon-as-eof-is-reached/57867/2 "2016-08-12T08:01:32Z")

</div>

This is currently not possible. Here is an open issue for this feature request: [https://github.com/elastic/beats/issues/880](https://github.com/elastic/beats/issues/880)

---

<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:** [August 12, 2016, 2:01pm UTC](https://discuss.elastic.co/t/can-you-configure-filebeat-to-exit-as-soon-as-eof-is-reached/57867/3 "2016-08-12T14:01:45Z")

</div>

As this is not possible yet, I normally use `-httpprof :6060` to open the beats HTTP debugging endpoint and fetch number of published events about every second. This gives me the throughput. Search Beats forum for `expvar_rates.py` for python script showing the current rate + some average rate.

Using [collectbeat](https://github.com/urso/collectbeat) throughput info can be written to another/local elasticsearch instance for querying via kibana. Build might be broken from time to time + it might work with master most recent beats alpha only as I update from time to time to keep up with master branch (no versioning yet).

---

<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:** [September 1, 2016, 11:01pm UTC](https://discuss.elastic.co/t/can-you-configure-filebeat-to-exit-as-soon-as-eof-is-reached/57867/4 "2016-09-01T23:01:34Z")

</div>

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