elasticsearch.search.fetch
Fetch operationsDimensions:None
Summary
Counts fetch phase operations in two-phase search queries. After the query phase identifies matching documents, the fetch phase retrieves actual document content from shards. High fetch counts with slow query times suggest large result sets, inefficient from/size pagination (as noted in the deep pagination insight), or excessive field retrieval requiring optimization.
Interface Metrics (12)
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Sources







elasticsearch_index_stats_search_fetch_time_seconds_totalwww.dynatrace.com
elasticsearch.search.fetch.time.countgithub.com
indices_search_fetch_totalgithub.com
elasticsearch.search.fetch.total.countgithub.com
elasticsearch.primaries.search.fetch.timegithub.com
elasticsearch.primaries.search.fetch.totalgithub.com
elasticsearch.search.fetch.currentgithub.com
elasticsearch.search.fetch.totalgithub.com
Related Insights (1)
Search Query Latency Degradationwarning
Search operations taking longer than acceptable thresholds (typically >500ms for p95) indicate performance issues from oversized result sets, complex aggregations, inefficient queries, or resource contention.
▸