# My lifecycle policy is not working

**URL:** <https://discuss.elastic.co/t/my-lifecycle-policy-is-not-working/332856>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [May 9, 2023, 3:00am UTC](https://discuss.elastic.co/t/my-lifecycle-policy-is-not-working/332856 "2023-05-09T03:00:03Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 9, 2023, 6:04am UTC](https://discuss.elastic.co/t/my-lifecycle-policy-is-not-working/332856/8 "2023-05-09T06:04:34Z")

</div>

When you use rollover alias is does not include the date...

Read the docs I actually gave you the solution...

Perhaps look at this

> [@Filebeat process different log paths and write data to seperate index,Without use of logstash and follow ILM/rollover alias defined in template](https://discuss.elastic.co/t/filebeat-process-different-log-paths-and-write-data-to-seperate-index-without-use-of-logstash-and-follow-ilm-rollover-alias-defined-in-template/332593/12):
>
> @PRASHANT_MEHTA Looks at this carefully this is minimal but does everything you ask. This is the order you need to do this as well ... BTW timeseries indices are of the pattern my-index-yyyy.mm.dd-000001 # Create Common ILM Policy PUT \_ilm/policy/mis-monitoring-common-policy { "policy": { "phases": { "hot": { "actions": { "rollover": { "max\_age": "1d", "max\_size": "50gb" }, "set\_priority": { "priority": 10…

---

_[View the full topic](https://discuss.elastic.co/t/my-lifecycle-policy-is-not-working/332856)._
