# Less hits from ElastAlert than the count found in ES

**URL:** <https://discuss.elastic.co/t/less-hits-from-elastalert-than-the-count-found-in-es/84628>\
**Category:** Logstash\
**Created:** [May 4, 2017, 8:40pm UTC](https://discuss.elastic.co/t/less-hits-from-elastalert-than-the-count-found-in-es/84628 "2017-05-04T20:40:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mr\_chang7](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@mr\_chang7](https://discuss.elastic.co/u/mr_chang7)\
**Post date:** [May 4, 2017, 8:40pm UTC](https://discuss.elastic.co/t/less-hits-from-elastalert-than-the-count-found-in-es/84628/1 "2017-05-04T20:40:36Z")

</div>

This is more likely real-time monitoring system, sending data by collectd and storing it into ES using LS. Given the same query string and window (in milliseconds) elastalert sometimes report less hits than what I can find in the ES. I guess the elastalert might send the query slightly early (few seconds) before the data actually come down to the elasticsearch. It misses 1 or 2 hits even though the full data events are found in ES. Can I configure the elastalert to query with a slight delay? Or am I guessing in a wrong way?

---

<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:** [June 1, 2017, 8:44pm UTC](https://discuss.elastic.co/t/less-hits-from-elastalert-than-the-count-found-in-es/84628/2 "2017-06-01T20:44:40Z")

</div>

Closed on June 1, 2017, 8:44pm UTC

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