From 9cb2eec2fc652fff6dcab5657ddc2f55cc41e612 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Mon, 15 Sep 2025 14:21:36 +0100 Subject: [PATCH 1/3] Add minor clarification for data streams page I've slightly updated the intro sentence with a focus on the distinction/conceptual relationship between an index and a data stream. Fixes #1565 --- manage-data/data-store/data-streams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/data-store/data-streams.md b/manage-data/data-store/data-streams.md index 2a2e2d7a9f..af5c5fce35 100644 --- a/manage-data/data-store/data-streams.md +++ b/manage-data/data-store/data-streams.md @@ -13,7 +13,7 @@ products: # Data streams [data-streams] -A data stream lets you store append-only time series data across multiple indices while giving you a single named resource for requests. Data streams are well-suited for logs, events, metrics, and other continuously generated data. +A data stream represents an index abstraction that's optimized for storing append-only time series data. It stores data across multiple backing indices while giving you a single named resource to use for requests. Data streams are well-suited for logs, events, metrics, and other continuously generated data. You can submit indexing and search requests directly to a data stream. The stream automatically routes the request to backing indices that store the stream’s data. You can use [{{ilm}} ({{ilm-init}})](../lifecycle/index-lifecycle-management.md) to automate the management of these backing indices. For example, you can use {{ilm-init}} to automatically move older backing indices to less expensive hardware and delete unneeded indices. {{ilm-init}} can help you reduce costs and overhead as your data grows. From d0ecfff12581f7ce394dcc536d8a0b218ffe6069 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Mon, 15 Sep 2025 14:35:58 +0100 Subject: [PATCH 2/3] Add minor clarification re template and ILM policy --- manage-data/data-store/data-streams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/data-store/data-streams.md b/manage-data/data-store/data-streams.md index af5c5fce35..5b2fa22250 100644 --- a/manage-data/data-store/data-streams.md +++ b/manage-data/data-store/data-streams.md @@ -39,7 +39,7 @@ A data stream consists of one or more [hidden](elasticsearch://reference/elastic :alt: data streams diagram ::: -A data stream requires a matching [index template](templates.md). The template contains the mappings and settings used to configure the stream’s backing indices. +A data stream requires a matching [index template](templates.md). The template contains the mappings and settings used to configure the stream’s backing indices and defines the {{ilm-init}} policy that the data stream uses. Every document indexed to a data stream must contain a `@timestamp` field, mapped as a [`date`](elasticsearch://reference/elasticsearch/mapping-reference/date.md) or [`date_nanos`](elasticsearch://reference/elasticsearch/mapping-reference/date_nanos.md) field type. If the index template doesn’t specify a mapping for the `@timestamp` field, {{es}} maps `@timestamp` as a `date` field with default options. From f5662f8a61665a9996d384f1f2a8180ef44fd3e1 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Tue, 16 Sep 2025 08:09:16 +0100 Subject: [PATCH 3/3] Peer review edits --- manage-data/data-store/data-streams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manage-data/data-store/data-streams.md b/manage-data/data-store/data-streams.md index 5b2fa22250..b7e8f6c6be 100644 --- a/manage-data/data-store/data-streams.md +++ b/manage-data/data-store/data-streams.md @@ -13,7 +13,7 @@ products: # Data streams [data-streams] -A data stream represents an index abstraction that's optimized for storing append-only time series data. It stores data across multiple backing indices while giving you a single named resource to use for requests. Data streams are well-suited for logs, events, metrics, and other continuously generated data. +A data stream acts as a layer of abstraction over a set of indices that are optimized for storing append-only time series data. It stores data across multiple backing indices while giving you a single named resource to use for requests. Data streams are well-suited for logs, events, metrics, and other continuously generated data. You can submit indexing and search requests directly to a data stream. The stream automatically routes the request to backing indices that store the stream’s data. You can use [{{ilm}} ({{ilm-init}})](../lifecycle/index-lifecycle-management.md) to automate the management of these backing indices. For example, you can use {{ilm-init}} to automatically move older backing indices to less expensive hardware and delete unneeded indices. {{ilm-init}} can help you reduce costs and overhead as your data grows.