# Not all log entries show up in the Elasticsearch indices **URL:** \ **Category:** Logstash\ **Created:** [April 1, 2019, 6:42pm UTC](https://discuss.elastic.co/t/not-all-log-entries-show-up-in-the-elasticsearch-indices/174845 "2019-04-01T18:42:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ebisu](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@Ebisu](https://discuss.elastic.co/u/Ebisu)\ **Post date:** [April 1, 2019, 6:42pm UTC](https://discuss.elastic.co/t/not-all-log-entries-show-up-in-the-elasticsearch-indices/174845/1 "2019-04-01T18:42:12Z")
Sorry for this very general question: I'm using Logstash to parse simple log files. I notice a difference in the number of entries between between what I get by using grep and what shows up in the indices. It's not that bit, around 0.1%–0.2%: like the Elasticsearch indices have 999,000 documents while with grep I get 1,000,000 log entries. The log files have a simple structure and I use the equivalent regex with grep as I use with grok. All logfiles show up in the sincedb file. I'd just would like to hear some hints how to approach this problem. I have no idea what could be the reason. ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [April 1, 2019, 7:24pm UTC](https://discuss.elastic.co/t/not-all-log-entries-show-up-in-the-elasticsearch-indices/174845/2 "2019-04-01T19:24:55Z")
Do you ever use a drop {} filter to discard entries? If so, under what circumstances? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 29, 2019, 7:24pm UTC](https://discuss.elastic.co/t/not-all-log-entries-show-up-in-the-elasticsearch-indices/174845/3 "2019-04-29T19:24:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.