stack es cluster health 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 cluster health [options]
Get the cluster health status.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--expand-wildcardsenum-
Expand wildcard expression to concrete indices that are open, closed or both.
Values: all, open, closed, hidden, none
Repeatable: pass
--expand-wildcardsmultiple times to supply more than one value --levelenum-
Return health information at a specific level of detail.
Values: cluster, indices, shards
--local- If true, retrieve information from the local node only. If false, retrieve information from the master node.
--master-timeoutstring- The period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.
--timeoutstring- The period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error.
--wait-for-active-shardsstring- Wait for the specified number of active shards.
Use
allto wait for all shards in the cluster to be active. Use0to not wait. --wait-for-eventsenum-
Wait until all currently queued events with the given priority are processed.
Values: immediate, urgent, high, normal, low, languid
--wait-for-nodesstring- Wait until the specified number (N) of nodes is available.
It also accepts
>=N,<=N,>Nand<N. Alternatively, use the notationsge(N),le(N),gt(N), andlt(N). --wait-for-no-initializing-shards- Wait (until the timeout expires) for the cluster to have no shard initializations. If false, the request does not wait for initializing shards.
--wait-for-no-relocating-shards- Wait (until the timeout expires) for the cluster to have no shard relocations. If false, the request not wait for relocating shards.
--wait-for-statusenum-
Wait (until the timeout expires) for the cluster to reach a specific health status (or a better status). A green status is better than yellow and yellow is better than red. By default, the request does not wait for a particular status.
Values: green, yellow, red, unknown, unavailable
--indexstring-
A comma-separated list of data streams, indices, and index aliases that limit the request. Wildcard expressions (
*) are supported. To target all data streams and indices in a cluster, omit this parameter or use _all or*.Repeatable: 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