Skip to content

Commit 06f4c88

Browse files
committed
add intro sentence
1 parent 8611807 commit 06f4c88

File tree

2 files changed

+4
-0
lines changed

2 files changed

+4
-0
lines changed

manage-data/lifecycle/data-stream.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ A data stream lifecycle also supports downsampling the data stream backing indic
2424

2525
## Availability
2626

27+
Note the availability of data stream lifecycle to ensure that it's applicable for your use case:
28+
2729
* Data stream lifecycle is supported only for data streams and cannot be used with standalone indices.
2830

2931
* Like {{ilm-cap}} ({{ilm-init}}), data stream lifecycle is supported in both {{ecloud}} and self-managed environments. Data stream lifecycle is less feature rich than {{ilm-init}} and is focused on simplicity. For a detailed comparison refer to [Data lifecycle](/manage-data/lifecycle.md).

manage-data/lifecycle/index-lifecycle-management.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ products:
2323

2424
## Availability
2525

26+
Note the availability of {{ilm-init}} to ensure that it's applicable for your use case:
27+
2628
* {{ilm-init}} is supported for both data streams and standalone indices:
2729

2830
* **Data stream:** A [data stream](/manage-data/data-store/data-streams.md) acts as a layer of abstraction over a set of indices that contain append-only, time series data. You can configure {{ilm-init}} using a data stream as a single named resource, so that rollover and any other configured actions are performed on the data stream's backing indices automatically.

0 commit comments

Comments
 (0)