Get data streams
- GET /_data_stream/{name}
- GET /_data_stream
Get information about one or more data streams.
Required authorization
- Index privileges view_index_metadata
Query parameters
-
expand_wildcardsstring · default: open -
Type of data stream that wildcard patterns can match. Supports comma-separated values, such as
open,hidden.Supported values include:
all: Match any data stream or index, including hidden ones.open: Match open, non-hidden indices. Also matches any non-hidden data stream.closed: Match closed, non-hidden indices. Also matches any non-hidden data stream. Data streams cannot be closed.hidden: Match hidden data streams and hidden indices. Must be combined withopen,closed, orboth.none: Wildcard expressions are not accepted.
-
Values:
allopenclosedhiddennone -
include_defaultsboolean · default: false -
If true, returns all relevant default configurations for the index template.
Response
-
data_streamsobjectrequired -
_metaobject -
Custom metadata for the stream, copied from the
_metaobject of the stream’s matching index template. If empty, the response omits this property. -
generationnumberrequired -
Current generation for the data stream. This number acts as a cumulative count of the stream’s rollovers, starting at 1.
-
If
true, the data stream is hidden. -
ilm_policystring -
Name of the current ILM lifecycle policy in the stream’s matching index template. This lifecycle policy is set in the
index.lifecycle.namesetting. If the template does not include a lifecycle policy, this property is not included in the response. NOTE: A data stream’s backing indices may be assigned different lifecycle policies. To retrieve the lifecycle policy for individual backing indices, use the get index settings API. -
next_generation_managed_byrequired -
Name of the lifecycle system that'll manage the next generation of the data stream.
-
Values:
Index Lifecycle ManagementData stream lifecycleUnmanaged -
prefer_ilmbooleanrequired -
Indicates if ILM should take precedence over DSL in case both are configured to managed this data stream.
-
indicesobjectrequired -
Array of objects containing information about the data stream’s backing indices. The last item in this array contains information about the stream’s current write index.
-
lifecycleobject -
Contains the configuration for the data stream lifecycle of this data stream.
-
data_retentionstring -
If defined, every document added to this data stream will be stored at least for this time frame. Any time after this duration the document could be deleted. When empty, every document in this data stream will be stored indefinitely.
-
retention_determined_by -
Configuration source that can influence the retention of a data stream.
-
Values:
data_stream_configurationdefault_global_retentionmax_global_retentiondefault_failures_retention -
downsamplingobject -
The list of downsampling rounds to execute as part of this downsampling configuration
-
downsampling_method -
The method used to downsample the data. There are two options
aggregateandlast_value. It requiresdownsamplingto be defined. Defaults toaggregate. -
Values:
aggregatelast_value -
enabledboolean · default: true -
If defined, it turns data stream lifecycle on/off (
true/false) for this data stream. A data stream lifecycle that's disabled (enabled:false) will have no effect on the data stream. -
frozen_afterstring -
The period after which data stream backing indices are automatically converted to partially mounted searchable snapshots. This field is valid only on main data stream lifecycles and cannot be set on failure-store lifecycles.
-
rolloverobject -
The conditions which will trigger the rollover of a backing index as configured by the cluster setting
cluster.lifecycle.default.rollover. This property is an implementation detail and it will only be retrieved when the query paraminclude_defaultsis set to true. The contents of this field are subject to change. -
replicatedboolean -
If
true, the data stream is created and managed by cross-cluster replication and the local cluster can not write into this data stream or change its mappings. -
rollover_on_writebooleanrequired -
If
true, the next write to this data stream will trigger a rollover first and the document will be indexed in the new backing index. If the rollover fails the indexing request will fail too. -
settingsobjectrequired -
The settings specific to this data stream that will take precedence over the settings in the matching index template.
-
mappingsobject -
The mappings specific to this data stream that will take precedence over the mappings in the matching index template.
-
statusrequired -
Health status of the data stream. This health status is based on the state of the primary and replica shards of the stream’s backing indices.
Supported values include:
green(orGREEN): All shards are assigned.yellow(orYELLOW): All primary shards are assigned, but one or more replica shards are unassigned. If a node in the cluster fails, some data could be unavailable until that node is repaired.red(orRED): One or more primary shards are unassigned, so some data is unavailable. This can occur briefly during cluster startup as primary shards are assigned.unknownunavailable
-
Values:
greenGREENyellowYELLOWredREDunknownunavailable -
systemboolean -
If
true, the data stream is created and managed by an Elastic stack component and cannot be modified through normal user interaction. -
templatestringrequired -
Name of the index template used to create the data stream’s backing indices. The template’s index pattern must match the name of this data stream.