# Trace query execution path

**URL:** <https://discuss.elastic.co/t/trace-query-execution-path/1808>\
**Category:** Elasticsearch\
**Created:** [June 3, 2015, 8:20am UTC](https://discuss.elastic.co/t/trace-query-execution-path/1808 "2015-06-03T08:20:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![moshere](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@moshere](https://discuss.elastic.co/u/moshere)\
**Post date:** [June 3, 2015, 8:20am UTC](https://discuss.elastic.co/t/trace-query-execution-path/1808/1 "2015-06-03T08:20:49Z")

</div>

Hi,  
Recently I added several analyzers including synonyms and phonetic plugin to our Elastic indices.  
I'm running several queries and I would like to understand the exact path that this query executed from the time it entered to Elastic until I got the results.  
For example I would like to understand which Analyzers triggered, which synonym words where chosen etc.  
I tried using slowlog however it present only the query without this information.

Let me know if there is something like this and how to enable it.

Thank you in advance,  
Moshe

---

<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:** [June 3, 2015, 12:18pm UTC](https://discuss.elastic.co/t/trace-query-execution-path/1808/2 "2015-06-03T12:18:28Z")

</div>

There is the [explain API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-explain.html) but that is for scoring. Apart from that there isn't anything at the moment.  
This is something we are discussing though.

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [June 3, 2015, 5:32pm UTC](https://discuss.elastic.co/t/trace-query-execution-path/1808/3 "2015-06-03T17:32:30Z")

</div>

Hi,

Couldn't you run ES under a debugger and trace everything?

## Otis

Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management  
Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/)

---

<div class="post-metadata">

**Author:** ![moshere](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@moshere](https://discuss.elastic.co/u/moshere)\
**Post date:** [June 3, 2015, 7:02pm UTC](https://discuss.elastic.co/t/trace-query-execution-path/1808/4 "2015-06-03T19:02:31Z")

</div>

Hi,  
Thank you.  
This is really great idea. Hopefully I'll understand the code 🙂

Moshe

---

<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:** [July 6, 2017, 12:09am UTC](https://discuss.elastic.co/t/trace-query-execution-path/1808/5 "2017-07-06T00:09:48Z")

</div>