# Rollover information for alias

**URL:** <https://discuss.elastic.co/t/rollover-information-for-alias/116778>\
**Category:** Elasticsearch\
**Created:** [January 24, 2018, 1:22am UTC](https://discuss.elastic.co/t/rollover-information-for-alias/116778 "2018-01-24T01:22:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [January 24, 2018, 1:22am UTC](https://discuss.elastic.co/t/rollover-information-for-alias/116778/1 "2018-01-24T01:22:51Z")

</div>

Hi All,

Once rollover is set against a alias, how do I see what is set? Should I have to refer to the codebase always? Is there any API that can tell me what rollover strategy is applied to an alias.

Regards  
Karrthik R

---

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [January 25, 2018, 2:09am UTC](https://discuss.elastic.co/t/rollover-information-for-alias/116778/2 "2018-01-25T02:09:49Z")

</div>

Given that rollover data is not stored and a explict API trigger, i have to maintain it outside. Thought of checking what was the last rollover applied to an alias.

Can be closed by admin. If possible, we can add feature in later release to perform auto rollover only the rollover is set instead of issuing the command again.

---

<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 22, 2018, 2:10am UTC](https://discuss.elastic.co/t/rollover-information-for-alias/116778/3 "2018-02-22T02:10:33Z")

</div>

Closed on February 22, 2018, 2:10am UTC

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