ElasticsearchMetricelasticsearch.node.operations.time
Node operation time
OpenTelemetry (1)Summary
Measures the cumulative time spent performing indexing, deletion, and other write operations. Rising values indicate increasing indexing workload or degrading performance. When combined with operation counts, this metric reveals average operation latency, helping identify write throughput bottlenecks from merge throttling, disk I/O saturation, or CPU contention.
Interface Metrics (1)
Technical Annotations (3)
Technical References (3)
ILMcomponentdownsamplingconceptforce mergecomponentRelated Insights (4)
Refresh operations make indexed documents searchable by writing in-memory buffer to disk segments. Default 1-second interval creates overhead that scales with indexing rate. When refresh time exceeds interval, indexing throughput collapses and latency spikes.
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 queries can cause significant coordination overhead, network traffic, and timeout issues when remote clusters are slow or have high latency.