# Create the correct ILM policy **URL:** \ **Category:** Kibana\ **Tags:** ilm-index-lifecycle-management\ **Created:** [September 25, 2019, 4:06am UTC](https://discuss.elastic.co/t/create-the-correct-ilm-policy/200956 "2019-09-25T04:06:07Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kastu707](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kastu707/32/54560_2.png) [@kastu707](https://discuss.elastic.co/u/kastu707)\ **Post date:** [September 25, 2019, 4:06am UTC](https://discuss.elastic.co/t/create-the-correct-ilm-policy/200956/1 "2019-09-25T04:06:07Z")
Hello to the community! I'm new to the stack and I have a small PROD deployment (approx 50 network devices syslog logs severity 0-4. Not sure yet about the number of hits/day ) for my client. Right now I only have one node on my cluster. We did a POC before (by someone who left the company) and at that time he used curator to manage index. But I would like to use the build-in ILM functionality to simplify operations. Here's the requirement : > Logs are kept at least 1 year. Audit trails regarding the last 3 months must be immediately available through the interface. For now, I'm still on the testing phase and I decided to create a daily index (logstash output section). I have been struggling a bit on the ILM interface and I'm wondering if daily index is such a good idea. I thought about a hot phase with a maximum age (90days) then a delete phase but I see that the delete one is linked to rollover...but I don't see the use for it! Reading the documentation and googling it somehow made things even more confusing ☹ Thanks again for the help! ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [September 25, 2019, 1:39pm UTC](https://discuss.elastic.co/t/create-the-correct-ilm-policy/200956/2 "2019-09-25T13:39:42Z")
Hi @kastu707, Thanks for reaching out. This blog article might be able to help you [Implementing Hot-Warm-Cold in Elasticsearch with Index Lifecycle Management | Elastic Blog](https://www.elastic.co/blog/implementing-hot-warm-cold-in-elasticsearch-with-index-lifecycle-management) It gives an example on ILM using the API as well as through the UI. > I thought about a hot phase with a maximum age (90days) then a delete phase but I see that the delete one is linked to rollover...but I don't see the use for it! By specifying a `max_age` for the hot phase in the UI, you are enabling rollover. If rollover was not enabled on the hot phase, deletion would be based on days/hours from index creation. Also, this post details some of the benefits of the rollover pattern: [https://www.elastic.co/blog/managing-time-based-indices-efficiently](https://slack-redir.net/link?url=https%3A%2F%2Fwww.elastic.co%2Fblog%2Fmanaging-time-based-indices-efficiently) For further questions about ILM the [elasticsearch forum](https://discuss.elastic.co/c/elasticsearch) might be a better place to ask. ---
**Author:** ![kastu707](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kastu707/32/54560_2.png) [@kastu707](https://discuss.elastic.co/u/kastu707)\ **Post date:** [September 26, 2019, 2:13am UTC](https://discuss.elastic.co/t/create-the-correct-ilm-policy/200956/3 "2019-09-26T02:13:58Z")
Thanks a lot @flash1293, I will have a look on it! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 24, 2019, 2:14am UTC](https://discuss.elastic.co/t/create-the-correct-ilm-policy/200956/4 "2019-10-24T02:14:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.