elasticsearch.search.query
Query operationsDimensions:None
Summary
Measures search query activity including operation counts, timing, and current in-flight queries. This metric provides visibility into query load patterns and performance characteristics. Spikes in query time or high counts of concurrent queries can indicate expensive query patterns, insufficient caching, or resource contention that degrades search latency for end users.
Interface Metrics (13)
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Dimensions:None
Sources










index_stats_search_query_time_seconds_totalgithub.com
elasticsearch.primaries.search.query.timegithub.com
elasticsearch.search.query.total.countgithub.com
elasticsearch_indices_search_query_totalwww.dynatrace.com
elasticsearch.primaries.search.fetch.currentgithub.com
elasticsearch.primaries.search.query.currentgithub.com
elasticsearch.search.query.time.countgithub.com
elasticsearch.index.search.query.totalgithub.com
elasticsearch.primaries.search.query.totalgithub.com
elasticsearch.search.query.currentgithub.com
elasticsearch.search.query.totalgithub.com
Related Insights (2)
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.
▸
Cross-Cluster Search Coordination Overheadwarning
Cross-cluster search queries can cause significant coordination overhead, network traffic, and timeout issues when remote clusters are slow or have high latency.
▸