In Kibana dev-console, I see a big difference between ES query took time and Kibana ellapsed time. Why ? [Capture d’écran 2020-10-02 à 10.49.34]

Hi @ebuildy - this post is explaining what "took" is measuring: Query timing: 'took' value and what I'm measuring In short it's how long the internals of Elasticsearch spent time on the request - everything outside of the cluster (JSON serializing, transmitting data, ...) is not included.

Explain difference between Kibana "time ellapsed" and query "took"

Elastic Stack Kibana

ebuildy (Thomas Decaux) October 2, 2020, 3:02pm 5

I really cant believe JSON serialization takes more time than the query itself .....

Topic		Replies	Views
Took is having a different value than the time ES is taking to show the result in Kibana Elasticsearch	6	550	April 4, 2019
Time Difference with "took" and python timer Elasticsearch	6	557	December 28, 2021
Profiling : "took" is much higher than all breakdown times Elasticsearch	2	478	April 9, 2018
Query timing: 'took' value and what I'm measuring Elasticsearch	7	46990	July 6, 2017
How to measure performance of kibana? Kibana	4	2123	July 6, 2017

Explain difference between Kibana "time ellapsed" and query "took"

Related topics