# Elasticsearch debugging percolator candidates

**URL:** <https://discuss.elastic.co/t/elasticsearch-debugging-percolator-candidates/228453>\
**Category:** Elasticsearch\
**Created:** [April 17, 2020, 5:16am UTC](https://discuss.elastic.co/t/elasticsearch-debugging-percolator-candidates/228453 "2020-04-17T05:16:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faiz\_Ahmed\_Mushtak\_H](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faiz_ahmed_mushtak_h/32/47387_2.png) [@Faiz\_Ahmed\_Mushtak\_H](https://discuss.elastic.co/u/Faiz_Ahmed_Mushtak_H)\
**Post date:** [April 17, 2020, 5:16am UTC](https://discuss.elastic.co/t/elasticsearch-debugging-percolator-candidates/228453/1 "2020-04-17T05:16:00Z")

</div>

I'd like to know which package should I enable the logger of to know the potential candidates ES is going to try percolating against?

Also, as part of percolator response, why can't ES return a metric saying how many candidates were tried? This is a good metric to know whenever percolators start slowing down

---

<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:** [May 15, 2020, 5:16am UTC](https://discuss.elastic.co/t/elasticsearch-debugging-percolator-candidates/228453/2 "2020-05-15T05:16:00Z")

</div>

Closed on May 15, 2020, 5:16am UTC

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