Technologies/Elasticsearch/elasticsearch.node.operations.get.time
ElasticsearchElasticsearchMetric

elasticsearch.node.operations.get.time

Get operation time
Dimensions:None
Available on:PrometheusPrometheus (4)DatadogDatadog (9)DynatraceDynatrace (2)OpenTelemetryOpenTelemetry (1)

Summary

Measures the cumulative time spent performing get operations by ID on a node. This counter tracks total latency for document retrieval operations since node startup. Increasing rates indicate growing get operation latency, potentially from disk I/O slowness or index size growth. Comparing time against operation counts reveals average get duration, useful for diagnosing document lookup performance issues.

Interface Metrics (16)
PrometheusPrometheus
Total get time in seconds
Dimensions:None
DatadogDatadog
The total time spent on get requests from the primary shards.
Dimensions:None
DatadogDatadog
The total time spent on get requests where the document was missing submitted as a count.
Dimensions:None
PrometheusPrometheus
Total time of get missing in seconds
Dimensions:None
DatadogDatadog
The total time spent on get requests where the document existed submitted as a count.
Dimensions:None
PrometheusPrometheus
Total time get exists in seconds
Dimensions:None
DynatraceDynatrace
Get time in seconds
Dimensions:None
PrometheusPrometheus
Total get time in seconds
Dimensions:None
DatadogDatadog
The total time spent on get requests submitted as a count.
Dimensions:None
OpenTelemetryOpenTelemetry
The time spent on hits and misses resulting from GET operations.
Dimensions:None
DatadogDatadog
The total time spent on get requests.
Dimensions:None
DynatraceDynatrace
Get time in seconds
Dimensions:None
DatadogDatadog
The total time spent on get requests where the document existed.
Dimensions:None
DatadogDatadog
The total time spent on get requests where the document was missing.
Dimensions:None
DatadogDatadog
The total time spent on get requests from the primary shards where the document existed.
Dimensions:None
DatadogDatadog
The total time spent on get requests from the primary shards where the document was missing.
Dimensions:None
Sources
indices_get_time_secondsgithub.com
elasticsearch.primaries.get.timegithub.com
elasticsearch.get.missing.time.countgithub.com
elasticsearch.get.exists.time.countgithub.com
elasticsearch_index_stats_get_time_seconds_totalwww.dynatrace.com
elasticsearch.get.time.countgithub.com
elasticsearch.node.operations.get.timegithub.com
elasticsearch.get.timegithub.com
elasticsearch.get.exists.timegithub.com
elasticsearch.get.missing.timegithub.com
elasticsearch.primaries.get.exists.timegithub.com
elasticsearch.primaries.get.missing.timegithub.com
Related Insights (1)
Document GET Operation Latencyinfo

High latency for document GET operations indicates potential issues with routing, shard location, or storage performance when retrieving specific documents by ID.

▸