Unfortunately the problem with the Rollover API / ILM index bootstrapping is you need to know in advance the all the possible names of the "data flows" you will be receiving in the cluster, so that a write rollover alias is ready on Elasticsearch side.
This is detailed in this Github issue and Elasticsearch is evolving to make "unknown" indices auto-bootstrap the indices with 2 concepts:
You will need to put in place an index template to associated the indices myprefix-mass-* and myprefix-another-* the rollover_alias respectively of myprefix-mass and myprefix-another and a ILM policy.
I'm guessing you could use an http filter to do the put of the template, but that strikes me as something that could go very wrong if you have noise in your input.
If your dataset really does only have a few values for indexname then it would be OK, but every additional value adds cost.
Thanks Luca_Belluccini , thanks Badger so, the easyest way to solve this will be using myprefix* index template and then adding a ILM after the index is created?
The policy name can be the same or different for both.
Other common settings across both indices can be set using another template which matches both. E.g.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.