stack es indices stats cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack es indices stats [options]
Get index statistics.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--completion-fieldsstring-
Comma-separated list or wildcard expressions of fields to include in fielddata and suggest statistics.
Repeatable: pass
--completion-fieldsmultiple times to supply more than one value --expand-wildcardsenum-
Type of index that wildcard patterns can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. Supports comma-separated values, such as
open,hidden.Values: all, open, closed, hidden, none
Repeatable: pass
--expand-wildcardsmultiple times to supply more than one value --fielddata-fieldsstring-
Comma-separated list or wildcard expressions of fields to include in fielddata statistics.
Repeatable: pass
--fielddata-fieldsmultiple times to supply more than one value --fieldsstring-
Comma-separated list or wildcard expressions of fields to include in the statistics.
Repeatable: pass
--fieldsmultiple times to supply more than one value --forbid-closed-indices- If true, statistics are not collected from closed indices.
--groupsstring-
Comma-separated list of search groups to include in the search statistics.
Repeatable: pass
--groupsmultiple times to supply more than one value --include-segment-file-sizes- If true, the call reports the aggregated disk usage of each one of the Lucene index files (only applies if segment stats are requested).
--include-unloaded-segments- If true, the response includes information from segments that are not loaded into memory.
--levelenum-
Indicates whether statistics are aggregated at the cluster, indices, or shards level.
Values: cluster, indices, shards
--metricenum-
Comma-separated list of metrics used to limit the request.
Values: _all, store, indexing, get, search, merge, flush, refresh, query_cache, fielddata, docs, warmer, completion, segments, translog, request_cache, recovery, bulk, shard_stats, mappings, dense_vector, sparse_vector
Repeatable: pass
--metricmultiple times to supply more than one value --indexstring-
A comma-separated list of index names; use
_allor empty string to perform the operation on all indicesRepeatable: pass
--indexmultiple times to supply more than one value --error-trace- When set to
trueElasticsearch will include the full stack trace of errors when they occur. --filter-pathstring-
Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.
Repeatable: pass
--filter-pathmultiple times to supply more than one value --human- When set to
truewill return statistics in a format suitable for humans. For example"exists_time": "1h"for humans and"exists_time_in_millis": 3600000for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines. --pretty- If set to
truethe returned JSON will be "pretty-formatted". Only use this option for debugging only. --input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON