Technologies/Elasticsearch/elasticsearch.node.fs.disk.available
ElasticsearchElasticsearchMetric

elasticsearch.node.fs.disk.available

Available disk space bytes
Dimensions:None
Available on:DynatraceDynatrace (1)PrometheusPrometheus (1)DatadogDatadog (2)OpenTelemetryOpenTelemetry (1)

Summary

Reports available disk space on the node's filesystem, tracking free capacity for index data growth. Elasticsearch enforces disk watermark thresholds that prevent indexing when space falls below configured limits. Approaching watermarks triggers shard relocations (see "Disk Watermark Shard Relocation Storm" insight), while exhausting space causes indexing failures and potential red cluster status, making this metric critical for capacity management.

Interface Metrics (5)
DynatraceDynatrace
Filesystem available in bytes
Dimensions:None
PrometheusPrometheus
Available space on block device in bytes
Dimensions:None
DatadogDatadog
The free disk space available to Elasticsearch.
Dimensions:None
DatadogDatadog
The total number of bytes available to this Java virtual machine on this file store.
Dimensions:None
OpenTelemetryOpenTelemetry
The amount of disk space available to the JVM across all file stores for this node. Depending on OS or process level restrictions, this might appear less than free. This is the actual amount of free disk space the Elasticsearch node can utilise.
Dimensions:None
Sources
elasticsearch_filesystem_data_free_byteswww.dynatrace.com
filesystem_data_available_bytesgithub.com
elasticsearch.disk.availgithub.com
elasticsearch.fs.total.available_in_bytesgithub.com
elasticsearch.node.fs.disk.availablegithub.com
Related Insights (2)
Disk Watermark Shard Relocation Stormwarning

When any node crosses the low disk watermark (85% full by default), Elasticsearch starts relocating shards. Multiple nodes hitting watermarks simultaneously can trigger cascading relocations that overload cluster I/O and delay recovery.

▸
Index Lifecycle Management Stallswarning

ILM policies failing to execute transitions (hot to warm, warm to cold, delete) causes indices to accumulate in wrong tiers, wasting resources and degrading performance.

▸