yep that was a typo...Thanks - I corrected it so not to confuse others...
But the _ilm/explain command returned something interesting: "managed" : false"
So I double-checked the template to make sure that "rollover_alias" is pointing towards the correct alias. And is indeed index_from_logstash_test_alias. Also the index pattern seems ok... Maybe I am missing something ?
Here is also the output from GET /_alias/index_from_logstash_test_alias:
I am new to this Elastic thing so I could be wrong...
I think you should start over and deploy stuff in this order:
The ILM policy
The Index Template (with the index pattern and a reference to the policy)
The index itself (with the bootstrapping or maybe not)
If you are lucky, the system will see that your template has an index pattern that matches your new index, pick it, and use the referenced policy. If you are not so lucky, try adding a ridiculous high priority (999) to your template so it has a better chance of getting matched and picked.
Good idea Stephen, thanks. However I already had (in another cluster) a similar index rotation policy that worked fine with "index_from_logstash_test_alias*"
So I tried this: I directly tried POST index_from_logstash_test_alias/_rollover and it worked!
So after this _ilm_explain indicated that a new index is created and is managed by the policy index_from_logstash_test_alias-000002
(yet index_from_logstash_test_alias-000001 is still not managed). So I guess the next rollover will occur automatically after one day.
I am not sure what was the problem - maybe bootstraping the first index should have been done via the template