# How to interpret Indexing Latency , Search Latency **URL:** \ **Category:** Kibana\ **Created:** [April 13, 2020, 1:47pm UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780 "2020-04-13T13:47:21Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\ **Post date:** [April 13, 2020, 1:47pm UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/1 "2020-04-13T13:47:22Z")
How to interpret Indexing Latency , Search Latency from Kibana Stack monitoring dashboard I didn't find references about this documentation. ---
**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\ **Post date:** [April 13, 2020, 4:09pm UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/2 "2020-04-13T16:09:49Z")
Hi @nages, `Search Latency` is `time/count` for search or indexing events. For example, if you look at current metrics via`ES_URL/_stats`, `Search Latency` is calculated by dividing `_all.total.search.query_time_in_millis / _all.total.search.query_total`. In the Kibana Stack Monitoring UI, most charts show rates rather than raw values, so the chart will reflect the changes in the above math over time. Does that help? ---
**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\ **Post date:** [April 13, 2020, 4:12pm UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/3 "2020-04-13T16:12:35Z")
Is there any documentation that mentions all the details . I had see in the elastic. co documentations, there isn't any reference ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [April 13, 2020, 4:35pm UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/4 "2020-04-13T16:35:40Z")
> [@nages](#): > > Indexing Latency , Search Latency There are numerous things that can affect your query performance such as poorly constructed queries, improperly configured Elasticsearch clusters, JVM memory, garbage collection issues, etc. Without a doubt, query/search latency is a metric that has a direct impact on users, and it’s essential that you receive alerts when there’s an anomaly. Tracking the request rate along with query latency provides an overview of how much a system is used. Putting the request latency together with the request rate into a graph immediately provides an overview of how much the system is used and how it responds to it. copying @chrisronline for further inputs. Thanks Rashmi ---
**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\ **Post date:** [April 13, 2020, 4:44pm UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/5 "2020-04-13T16:44:16Z")
Thanks for your quick response. I am also looking for the documentation about all the terminology referred in "Stack monitoring" dashboard . > [Elastic Demos](https://demo.elastic.co/app/monitoring#/elasticsearch?_g=(cluster_uuid:hSYwUf4eRS-1JiJv5YenfQ,inSetupMode:!t,refreshInterval:(pause:!f,value:10000),time:(from:'2020-04-12T19:21:09.287Z',to:'2020-04-13T13:03:39.757Z'))) ---
**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\ **Post date:** [April 14, 2020, 4:17am UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/6 "2020-04-14T04:17:46Z")
It seems there is no response even for the "simple" questions like above - even after 12 hours .. I am aware of the rules of the community that everyone is busy and shouldn't be expecting a response soon. However, it is not recommended practice to take a lot of time for a simple questions like this. Not sure whom to reach out ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [April 14, 2020, 4:24am UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/7 "2020-04-14T04:24:19Z")
Have you checked out this documentation link: [https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-stats.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-stats.html) Few other relevant links: [https://www.elastic.co/guide/en/kibana/current/elasticsearch-metrics.html](https://www.elastic.co/guide/en/kibana/current/elasticsearch-metrics.html) [https://www.elastic.co/guide/en/kibana/current/monitoring-data.html](https://www.elastic.co/guide/en/kibana/current/monitoring-data.html) Thanks Rashmi ---
**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\ **Post date:** [April 14, 2020, 6:05am UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/8 "2020-04-14T06:05:08Z")
hmm, thanks for sharing "three" links for a simple explanation of the terminology used in the dashboard . Unfortunately , none of the links have the details Would you mind sharing specific phrases if you happened to find any . ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 12, 2020, 6:05am UTC](https://discuss.elastic.co/t/how-to-interpret-indexing-latency-search-latency/227780/9 "2020-05-12T06:05:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.