Skip to content

Commit d56fc7e

Browse files
committed
Minor fixes post feedback
1 parent fe45164 commit d56fc7e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

manage-data/lifecycle/rollup/migrating-from-rollup-to-downsampling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ mapped_pages:
44
- https://www.elastic.co/guide/en/elasticsearch/reference/current/rollup-migrating-to-downsampling.html
55
applies_to:
66
stack: ga
7-
serverless: ga
7+
serverless: unavailable
88
products:
99
- id: elasticsearch
1010
---
@@ -19,7 +19,7 @@ Rollup and downsampling are two different features that allow historical metrics
1919
The following aspects of downsampling are easier or more robust:
2020

2121
* No need to schedule jobs. Downsampling is integrated with Index Lifecycle Management (ILM) and Data Stream Lifecycle (DSL).
22-
* No separate search API. Downsampled indices can be accessed via the search API and ES|QL.
22+
* No separate search API. Downsampled indices can be accessed via the search API and {{esql}}.
2323
* No separate rollup configuration. Downsampling uses the time series dimension and metric configuration from the mapping.
2424

2525
It isn’t possible to migrate all rollup usages to downsampling. The main requirement is that the data should be stored in Elasticsearch as [time series data stream (TSDS)](../../data-store/data-streams/time-series-data-stream-tsds.md). Rollup usages that basically roll the data up by time and all dimensions can migrate to downsampling.

0 commit comments

Comments
 (0)