Technologies/Elasticsearch/elasticsearch.index.segments.count
ElasticsearchElasticsearchMetric

elasticsearch.index.segments.count

Segment count
Dimensions:None
Available on:DatadogDatadog (2)PrometheusPrometheus (2)OpenTelemetryOpenTelemetry (1)DynatraceDynatrace (1)

Summary

Tracks the number of Lucene segments per index. Segments are immutable storage units created during indexing. Too many segments degrade search performance and consume file descriptors. Too few large segments slow down merges and recovery. The excessive shard count insight extends to segment management—optimal segment counts balance search speed with merge overhead.

Interface Metrics (6)
DatadogDatadog
The number of indices in the cluster.
Dimensions:None
PrometheusPrometheus
Count of index segments on this node
Dimensions:None
OpenTelemetryOpenTelemetry
Number of segments of an index.
Dimensions:None
DynatraceDynatrace
Number of segments
Dimensions:None
PrometheusPrometheus
Current number of segments with only primary shards on all nodes
Dimensions:None
DatadogDatadog
The number of segments in an index shard.
Dimensions:None
Related Insights (2)
Merge Throttling Write Amplificationwarning

Background segment merges consolidate small Lucene segments into larger ones, reducing file count but consuming I/O. Default throttling (20MB/s) prevents merge backlog from overwhelming cluster, but excessive throttling causes segment explosion and query performance degradation.

Segment Merge Backlog Causing Query Slowdownwarning

Background segment merges consolidate small Lucene segments into larger ones, reducing file count. When merge rate cannot keep pace with segment creation, segment count explodes causing slow queries and increased memory usage.