# Problem with elapsed plugin

**URL:** https://discuss.elastic.co/t/problem-with-elapsed-plugin/52689
**Category:** Logstash
**Created:** [June 14, 2016, 6:29am UTC](https://discuss.elastic.co/t/problem-with-elapsed-plugin/52689 "2016-06-14T06:29:55Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![pantheo](https://avatars.discourse-cdn.com/v4/letter/p/9de0a6/32.png) [@pantheo](https://discuss.elastic.co/u/pantheo)
#### Post date: [June 22, 2016, 9:03am UTC](https://discuss.elastic.co/t/problem-with-elapsed-plugin/52689/3 "2016-06-22T09:03:01Z")

</div>

I do not think that multiple hosts are the problem. I am using the elapsed filter plugin with a single elasticsearch node and have noticed the same problem as you.

While it works, for the majority of time, sometimes I get an elapsed\_end\_without\_start tag even though the start event is present.

One more problem I noticed is that if I do not add the **periodic\_flush** setting the **timeout** setting never kicks in.

The event is never marked as expired and therefore no **elapsed\_expired\_error** tag is generated (unless I add the **periodic\_flush** setting as mentioned above.

Is this a bug or the way it should works? I am asking because the **periodic\_flush** setting is marked as optional.

---

_[View the full topic](https://discuss.elastic.co/t/problem-with-elapsed-plugin/52689)._