Technologies/Elasticsearch/elasticsearch.node.translog.uncommitted.size
ElasticsearchElasticsearchMetric

elasticsearch.node.translog.uncommitted.size

Uncommitted translog bytes
Dimensions:None
Available on:DynatraceDynatrace (1)PrometheusPrometheus (1)DatadogDatadog (1)OpenTelemetryOpenTelemetry (1)

Summary

Measures the size of uncommitted operations in the transaction log before they are fsynced to disk. Large uncommitted translog sizes can indicate slow disk I/O or delayed refresh operations. This metric is critical for understanding data durability risk — if a node fails with a large uncommitted translog, more data may be at risk of loss during recovery.

Interface Metrics (4)
DynatraceDynatrace
Translog size in bytes
Dimensions:None
PrometheusPrometheus
Completion in bytes
Dimensions:None
DatadogDatadog
The size of the transaction log.
Dimensions:None
OpenTelemetryOpenTelemetry
Size of uncommitted transaction log operations.
Dimensions:None
Sources
elasticsearch_indices_translog_size_in_byteswww.dynatrace.com
indices_completion_size_in_bytesgithub.com
elasticsearch.indices.translog.size_in_bytesgithub.com
elasticsearch.node.translog.uncommitted.sizegithub.com
Related Insights (1)
Translog Accumulation Riskwarning

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.

▸