Technologies/Elasticsearch/elasticsearch.indices.recovery
ElasticsearchElasticsearchMetric

elasticsearch.indices.recovery

Index recovery operations
Dimensions:None
Available on:DatadogDatadog (4)PrometheusPrometheus (1)

Summary

Provides statistics about ongoing index recovery operations, including peer recovery (replica shard initialization) and snapshot recovery. Recovery activity consumes network bandwidth, disk I/O, and CPU resources. High recovery counts indicate shard relocations, node additions, or failures requiring data synchronization. Prolonged recovery times may signal resource constraints or network issues impacting cluster resilience.

Interface Metrics (5)
DatadogDatadog
The total time recoveries waited due to throttling [v1.5.0+].
Dimensions:None
PrometheusPrometheus
Throttle time for index store in seconds
Dimensions:None
DatadogDatadog
The number of ongoing recoveries for which a shard serves as a source [v1.5.0+].
Dimensions:None
DatadogDatadog
The number of ongoing recoveries for which a shard serves as a target [v1.5.0+].
Dimensions:None
DatadogDatadog
The total time recoveries waited due to throttling submitted as a count [v1.5.0+].
Dimensions:None
Sources
elasticsearch.indices.recovery.throttle_timegithub.com
indices_store_throttle_time_seconds_totalgithub.com
elasticsearch.indices.recovery.current_as_sourcegithub.com
elasticsearch.indices.recovery.current_as_targetgithub.com
elasticsearch.indices.recovery.throttle_time.countgithub.com
Related Insights (1)
Index Recovery Prolonged Durationwarning

Slow shard recovery after node failures or restarts delays cluster stabilization and can indicate network issues, disk I/O bottlenecks, or configuration problems.

▸