ElasticsearchMetricelasticsearch.node.operations.completed
Current running operations
Summary
Tracks total completed operations on a node, including indexing, deletions, updates, and queries. This cumulative counter provides a high-level view of node activity and throughput. Sharp drops indicate node failures or load balancer routing changes, while sustained increases validate that the node is actively processing requests.
Interface Metrics (18)
DatadogDatadogDatadogDatadogDatadog
OpenTelemetryDatadogDatadogDatadogDatadogRelated 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.
Heavy bulk indexing workload causes high CPU utilization, memory pressure, and increased indexing latency, potentially impacting concurrent search performance and cluster stability.
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.
Transaction log (translog) accumulates uncommitted operations between flushes. Excessive translog size increases recovery time after node failures and can indicate flush problems or configuration issues.