# Rollups and ILM

**URL:** https://discuss.elastic.co/t/rollups-and-ilm/214555
**Category:** Elasticsearch
**Created:** [January 10, 2020, 7:57am UTC](https://discuss.elastic.co/t/rollups-and-ilm/214555 "2020-01-10T07:57:25Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![RichardH](https://avatars.discourse-cdn.com/v4/letter/r/9de0a6/32.png) [@RichardH](https://discuss.elastic.co/u/RichardH)
#### Post date: [January 10, 2020, 7:57am UTC](https://discuss.elastic.co/t/rollups-and-ilm/214555/1 "2020-01-10T07:57:25Z")

</div>

Hi All,

A bit of a newbie question.

Am I correct in my understanding that Rollups do not delete any data. They just create new aggregate/summary indexes. I would need to set up ILM to delete old granular data from the original indices after rollup?

Then, when configuring rollups. If I set the latency buffer to 7d does that mean it only performs rollups on data older than 7 days?

The time bucket size under Date Histogram - does this set the granularity of the rolled up data. ie. if set to 60m the rolled up data will include 1 hour averages of the metrics selected. Is this correct?

Or should I be working with the Histogram interval width setting to control this? (or is it both)?

Metrics selects the metrics I want to collect.

So if (using the Rollups configuration in Kibana) I select:

```
   "Latency buffer (optional)" = 7d.
   "Time Bucket" size = 60m
    A list of Monitoring metrics under "Histogram" (e.g. beats_stats.metrics.apm- 
          server.decoder.deflate.content-length) with a Histogram interval of 100
    The same Monitoring metrics under "Metrics" (e.g. beats_stats.metrics.apm- 
           server.decoder.deflate.content-length) and select the "Average" check box

```

Would it then rollup all **Averages** in the chosen metrics that are older than 7d into 60min buckets?

I could then (assuming I don't want it anymore, set up the ILM policy on the original indexes to delete after 7 days.

Thanks

---

<div class="post-metadata">

### Author: ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [January 10, 2020, 2:28pm UTC](https://discuss.elastic.co/t/rollups-and-ilm/214555/2 "2020-01-10T14:28:58Z")

</div>

regarding integration with index lifecycle management, you may want to follow this issue on github: [https://github.com/elastic/elasticsearch/issues/48003](https://github.com/elastic/elasticsearch/issues/48003)

---

<div class="post-metadata">

### Author: ![birko](https://avatars.discourse-cdn.com/v4/letter/b/dbc845/32.png) [@birko](https://discuss.elastic.co/u/birko)
#### Post date: [January 23, 2020, 4:51pm UTC](https://discuss.elastic.co/t/rollups-and-ilm/214555/3 "2020-01-23T16:51:28Z")

</div>

Hi Alexander,  
so nowadays it's not possible to manage old rollup data with ILM? Do you have any proposal how to manage it without ILM effectively, please?

Thanks

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 20, 2020, 4:51pm UTC](https://discuss.elastic.co/t/rollups-and-ilm/214555/4 "2020-02-20T16:51:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
