# INFLIGHT\_EVENTS\_REPORT being logged every 5 seconds

**URL:** <https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759>\
**Category:** Logstash\
**Created:** [November 4, 2015, 3:29pm UTC](https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759 "2015-11-04T15:29:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![weevil](https://avatars.discourse-cdn.com/v4/letter/w/82dd89/32.png) [@weevil](https://discuss.elastic.co/u/weevil)\
**Post date:** [November 4, 2015, 3:29pm UTC](https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759/1 "2015-11-04T15:29:09Z")

</div>

I am seeing the following in my log every 5 seconds:

{:timestamp=\>"2015-11-04T09:18:47.164000-0600", :message=\>["INFLIGHT\_EVENTS\_REPORT", "2015-11-04T09:18:47-06:00", {"input\_to\_filter"=\>0, "filter\_to\_output"=\>0, "outputs"=\>[]}], :level=\>:warn}

What does this mean and how can I stop it?

It began after I did a restart on the logstash service.

---

<div class="post-metadata">

**Author:** ![jbiggley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbiggley/32/5643_2.png) [@jbiggley](https://discuss.elastic.co/u/jbiggley)\
**Post date:** [November 5, 2015, 2:14pm UTC](https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759/2 "2015-11-05T14:14:40Z")

</div>

Did you do a ps -ef | grep -i logstash to see if there are additional instances of logstash running?

---

<div class="post-metadata">

**Author:** ![cpattonj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cpattonj/32/4365_2.png) [@cpattonj](https://discuss.elastic.co/u/cpattonj)\
**Post date:** [November 5, 2015, 7:39pm UTC](https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759/3 "2015-11-05T19:39:29Z")

</div>

It means that logstash is still draining events that won't necessarily be persistent should you initiate another SIGTERM against the logstash instance... from what I gather it's telling you to "wait" for it to finish draining out it's buffer.

Personally my instance has been doing this for a good long while so I'm not sure when I'm supposed to assume it's done or if it's buffer is just ginormous.

@jbiggley, yes and no other instances are running

---

<div class="post-metadata">

**Author:** ![jbiggley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbiggley/32/5643_2.png) [@jbiggley](https://discuss.elastic.co/u/jbiggley)\
**Post date:** [November 9, 2015, 11:42pm UTC](https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759/4 "2015-11-09T23:42:38Z")

</div>

We see this periodically when the buffer empties. If your batch\_size is set to an exceptionally high number, if you don't have enough worker processes assigned to the output, if you are groking the heck out of the data and haven't assigned enough grok workers... There are lots of reasons why this might take a while.

However, it should stop within due time. The other option is to hit ^C again or kill the running process.

---

<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 6, 2017, 5:23am UTC](https://discuss.elastic.co/t/inflight-events-report-being-logged-every-5-seconds/33759/5 "2017-07-06T05:23:18Z")

</div>