ElasticsearchMetricelasticsearch.os.cpu.usage
OS CPU percent
Summary
Measures CPU utilization as a percentage of total CPU capacity available to the operating system. This metric provides real-time CPU demand visibility across all processes. Values consistently above 80% indicate CPU saturation that degrades query response times and indexing throughput (see "CPU Saturation During Indexing" insight). Correlation with indexing rates helps distinguish between search-driven and indexing-driven CPU consumption.
Interface Metrics (3)
OpenTelemetryRelated Insights (4)
Heavy indexing workload causes high CPU utilization and increased indexing latency, negatively impacting concurrent search performance.
Field data (inverted reverse index for aggregations) loads into JVM heap on first access and persists for segment lifetime. When circuit breaker limit or cache size is too small, frequent evictions cause repeated expensive field data loading, spiking CPU and heap pressure.
Heavy bulk indexing workload causes high CPU utilization, memory pressure, and increased indexing latency, potentially impacting concurrent search performance and cluster stability.
Improper distribution of shards or unbalanced node roles can cause resource hotspots where some nodes are overloaded while others are underutilized.