From fb599dc343ee7bfc91439988738948b5091976c7 Mon Sep 17 00:00:00 2001 From: James Rodewig <40268737+jrodewig@users.noreply.github.com> Date: Fri, 31 Jul 2020 16:10:57 -0400 Subject: [PATCH] [DOCS] Add rollups to `Tune for disk usage` (#60436) (#60542) Co-authored-by: Leaf-Lin <39002973+Leaf-Lin@users.noreply.github.com> --- docs/reference/how-to/disk-usage.asciidoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/reference/how-to/disk-usage.asciidoc b/docs/reference/how-to/disk-usage.asciidoc index be726569271..0a791a44cd2 100644 --- a/docs/reference/how-to/disk-usage.asciidoc +++ b/docs/reference/how-to/disk-usage.asciidoc @@ -184,3 +184,11 @@ structure, fields, and values together should improve the compression ratio. Due to the fact that multiple documents are compressed together into blocks, it is more likely to find longer duplicate strings in those `_source` documents if fields always occur in the same order. + +[discrete] +[[roll-up-historical-data]] +=== Roll up historical data + +Keeping older data can useful for later analysis but is often avoided due to +storage costs. You can use data rollups to summarize and store historical data +at a fraction of the raw data's storage cost. See <>.