stack es tasks list cli command

elastic stack es tasks list [options]

Get all tasks.

Behaviour flags:

--dry-run — validate all inputs and exit without performing any action

--actions string

A comma-separated list or wildcard expression of actions used to limit the request. For example, you can use cluser:* to retrieve all cluster-related tasks.

Repeatable: pass --actions multiple times to supply more than one value

--detailed

If true, the response includes detailed information about the running tasks. This information is useful to distinguish tasks from each other but is more costly to run.

--group-by enum

A key that is used to group tasks in the response. The task lists can be grouped either by nodes or by parent tasks.

Values: nodes, parents, none

--nodes string

A comma-separated list of node IDs or names that is used to limit the returned information.

Repeatable: pass --nodes multiple times to supply more than one value

--parent-task-id string

A parent task identifier that is used to limit returned information. To return all tasks, omit this parameter or use a value of -1. If the parent task is not found, the API does not return a 404 response code.

--timeout string

The period to wait for each node to respond. If a node does not respond before its timeout expires, the response does not include its information. However, timed out nodes are included in the node_failures property.

--wait-for-completion

If true, the request blocks until the operation is complete.

--error-trace

When set to true Elasticsearch will include the full stack trace of errors when they occur.

--filter-path string

Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.

Repeatable: pass --filter-path multiple times to supply more than one value

--human

When set to true will return statistics in a format suitable for humans. For example "exists_time": "1h" for humans and "exists_time_in_millis": 3600000 for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines.

--pretty

If set to true the returned JSON will be "pretty-formatted". Only use this option for debugging only.

--input-file string

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-fields string

comma-separated list of fields to include in output (dot-notation supported)

--output-template string

Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")

--json

output as JSON