# Tools for troubleshooting performance issues

**URL:** <https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [January 28, 2019, 5:29pm UTC](https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032 "2019-01-28T17:29:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zoldello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zoldello/32/38851_2.png) [@zoldello](https://discuss.elastic.co/u/zoldello)\
**Post date:** [January 28, 2019, 5:29pm UTC](https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032/1 "2019-01-28T17:29:28Z")

</div>

What are tools I can use to troubleshoot performance issues with Elasticsearch? I need something that can take search queries and give me hints on why they are slow. It would be nice if it gives suggestions too.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 28, 2019, 5:36pm UTC](https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032/2 "2019-01-28T17:36:14Z")

</div>

Have you looked at the explain API? That might help, but it won't give suggestions.

---

<div class="post-metadata">

**Author:** ![zoldello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zoldello/32/38851_2.png) [@zoldello](https://discuss.elastic.co/u/zoldello)\
**Post date:** [January 28, 2019, 6:25pm UTC](https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032/3 "2019-01-28T18:25:01Z")

</div>

No, it does not help. It was not detailed enough. I had a similar problem with Profile API. It does not break things down enough to allow me to find poor patterns.

---

<div class="post-metadata">

**Author:** ![osykora](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/osykora/32/41464_2.png) [@osykora](https://discuss.elastic.co/u/osykora)\
**Post date:** [February 5, 2019, 2:42pm UTC](https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032/4 "2019-02-05T14:42:42Z")

</div>

Well, what worked for me was a combination of the explain API and performance tests running regularly in Jenkins. I ran a single query manually with the explain param, investigated results and simply found an alternative query for any problematic part I found, modified it and executed performance tests.

Also, playing with shards, replicas, # of nodes, analyzers etc. helps, but only with performance tests in place, because you can't spot any potential difference with a single request.

I hope this helps.

---

<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:** [March 5, 2019, 2:42pm UTC](https://discuss.elastic.co/t/tools-for-troubleshooting-performance-issues/166032/5 "2019-03-05T14:42:47Z")

</div>

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