stack es rollup rollup-search cli command

elastic stack es rollup rollup-search --index <index> [options]

Search rolled-up data.

Behaviour flags:

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

--index string required

A comma-separated list of data streams and indices used to limit the request. This parameter has the following rules: * At least one data stream, index, or wildcard expression must be specified. This target can include a rollup or non-rollup index. For data streams, the stream's backing indices can only serve as non-rollup indices. Omitting the parameter or using _all are not permitted.

• Multiple non-rollup indices may be specified.
• Only one rollup index may be specified. If more than one are supplied, an exception occurs.
• Wildcard expressions (*) may be used. If they match more than one rollup index, an exception occurs. However, you can use an expression to match multiple non-rollup indices or data streams.

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

--rest-total-hits-as-int

Indicates whether hits.total should be rendered as an integer or an object in the rest search response

--typed-keys

Specify whether aggregation and suggester names should be prefixed by their respective types in the response

--aggregations string

Specifies aggregations.

--query string

Specifies a DSL query that is subject to some limitations.

--size number

Must be zero if set, as rollups work on pre-aggregated data.

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