Technologies/Elasticsearch/elasticsearch.index.shards.size
ElasticsearchElasticsearchMetric

elasticsearch.index.shards.size

Shard size bytes
Dimensions:None
Available on:DatadogDatadog (6)DynatraceDynatrace (4)PrometheusPrometheus (5)OpenTelemetryOpenTelemetry (2)

Summary

Measures the total storage size of all shards belonging to an index, including primary and replica shards. This metric is essential for capacity planning and identifying index bloat. Comparing shard sizes to document counts reveals storage efficiency and helps detect issues like mapping explosion or excessive field indexing driving up storage costs.

Interface Metrics (17)
DatadogDatadog
The number of primary shards in the index
Dimensions:None
DynatraceDynatrace
Deleted documents by shard
Dimensions:None
PrometheusPrometheus
Count of deleted documents on this shard
Dimensions:None
DatadogDatadog
The number of replica shards in the index
Dimensions:None
PrometheusPrometheus
Count of documents on this shard
Dimensions:None
DynatraceDynatrace
Shard size in bytes
Dimensions:None
PrometheusPrometheus
Store size of this shard
Dimensions:None
DatadogDatadog
The store size of primary shards in the index
Dimensions:None
DynatraceDynatrace
Index size in bytes
Dimensions:None
PrometheusPrometheus
Store size of data stream
Dimensions:None
DatadogDatadog
The total size of all the primary shards.
Dimensions:None
DynatraceDynatrace
Total count of shards
Dimensions:None
PrometheusPrometheus
Total shards per node
Dimensions:None
OpenTelemetryOpenTelemetry
The size of the shards assigned to this node.
Dimensions:None
OpenTelemetryOpenTelemetry
The size of the shards assigned to this index.
Dimensions:None
DatadogDatadog
Number of primary and replica shards assigned to the node.
Dimensions:None
DatadogDatadog
The store size of primary and replica shards in the index
Dimensions:None
Sources
elasticsearch.index.primary_shardsgithub.com
elasticsearch_indices_shards_docs_deletedwww.dynatrace.com
indices_shards_docs_deletedgithub.com
elasticsearch.index.replica_shardsgithub.com
elasticsearch.index.primary_store_sizegithub.com
elasticsearch.primaries.store.sizegithub.com
elasticsearch.node.shards.sizegithub.com
elasticsearch.shardsgithub.com
elasticsearch.index.store_sizegithub.com

Technical Annotations (11)

Configuration Parameters (1)
index.mapping.use_doc_values_skipperrecommended: true (default for TSDB), false (default for standard indices)
Controls whether doc values skippers are used instead of BKD indexes
Technical References (10)
wildcard field typesconceptbinary doc valuescomponentZstd compressionprotocoldoc_valuescomponentBKD indexcomponent@timestampcomponent_tsidcomponentTSDB codeccomponentsorted-set doc valuescomponentrun-length encodingconcept
Related Insights (5)
Excessive Shard Count Degrades Performancecritical

Too many shards consume cluster resources even when idle, causing slow queries and increased overhead. Rule of thumb: keep shards below 20 per GB of heap configured.

▸
Excessive Shard Count Degrading Performancecritical

Too many shards consume cluster resources even when idle, causing slow queries, increased overhead, and reduced stability. Rule of thumb: keep shards below 20 per GB of heap configured.

▸
Binary doc values compression can reduce storage footprint for wildcard fieldsinfo
▸
Doc values skippers enabled by default in TSDB reduce index footprintinfo
▸
Large numeric blocks for TSDB improve compression for multi-valued fieldsinfo
▸