2020-06-05 10:10:03 -04:00
|
|
|
[[data-streams]]
|
2020-06-10 14:03:46 -04:00
|
|
|
= Data streams
|
2020-06-11 11:32:09 -04:00
|
|
|
++++
|
|
|
|
<titleabbrev>Data streams</titleabbrev>
|
|
|
|
++++
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
A _data stream_ is a convenient, scalable way to ingest, search, and manage
|
|
|
|
continuously generated time-series data.
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
Time-series data, such as logs, tends to grow over time. While storing an entire
|
|
|
|
time series in a single {es} index is simpler, it is often more efficient and
|
|
|
|
cost-effective to store large volumes of data across multiple, time-based
|
|
|
|
indices. Multiple indices let you move indices containing older, less frequently
|
|
|
|
queried data to less expensive hardware and delete indices when they're no
|
|
|
|
longer needed, reducing overhead and storage costs.
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
A data stream is designed to give you the best of both worlds:
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-12 09:14:36 -04:00
|
|
|
* The simplicity of a single named resource you can use for requests
|
2020-06-11 11:32:09 -04:00
|
|
|
* The storage, scalability, and cost-saving benefits of multiple indices
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
You can submit indexing and search requests directly to a data stream. The
|
|
|
|
stream automatically routes the requests to a collection of hidden,
|
|
|
|
auto-generated indices that store the stream's data.
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-26 11:52:58 -04:00
|
|
|
You can use an <<indices-templates,index template>> and
|
2020-06-11 11:32:09 -04:00
|
|
|
<<index-lifecycle-management,{ilm} ({ilm-init})>> to automate the management of
|
|
|
|
these hidden indices. You can use {ilm-init} to spin up new indices, allocate
|
|
|
|
indices to different hardware, delete old indices, and take other automatic
|
|
|
|
actions based on age or size criteria you set. This lets you seamlessly scale
|
|
|
|
your data storage based on your budget, performance, resiliency, and retention
|
|
|
|
needs.
|
2020-06-05 10:10:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
[discrete]
|
2020-06-11 11:32:09 -04:00
|
|
|
[[when-to-use-data-streams]]
|
|
|
|
== When to use data streams
|
|
|
|
|
|
|
|
We recommend using data streams if you:
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
* Use {es} to ingest, search, and manage large volumes of time-series data
|
|
|
|
* Want to scale and reduce costs by using {ilm-init} to automate the management
|
|
|
|
of your indices
|
|
|
|
* Index large volumes of time-series data in {es} but rarely delete or update
|
|
|
|
individual documents
|
2020-06-05 10:10:03 -04:00
|
|
|
|
2020-06-10 14:03:46 -04:00
|
|
|
|
|
|
|
[discrete]
|
|
|
|
[[data-streams-toc]]
|
|
|
|
== In this section
|
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
* <<data-streams-overview>>
|
2020-06-10 14:03:46 -04:00
|
|
|
* <<set-up-a-data-stream>>
|
|
|
|
* <<use-a-data-stream>>
|
2020-06-16 16:20:32 -04:00
|
|
|
* <<data-streams-change-mappings-and-settings>>
|
2020-06-10 14:03:46 -04:00
|
|
|
|
2020-06-11 11:32:09 -04:00
|
|
|
|
|
|
|
include::data-streams-overview.asciidoc[]
|
2020-06-10 14:03:46 -04:00
|
|
|
include::set-up-a-data-stream.asciidoc[]
|
|
|
|
include::use-a-data-stream.asciidoc[]
|
2020-06-16 16:20:32 -04:00
|
|
|
include::change-mappings-and-settings.asciidoc[]
|