[FEATURE] ISM policy with Transform Job as one of the action #1603
Description
Is your feature request related to a problem?
I am working on transforming the data from index-raw-* to index-hourly-* now for that one option was rollup job but i don't want to change my dashboard so we are moving with transform job now problem which i am facing is if i run that transfrom job continously then there will be overlap in dashboard because in dashboard we are using index-* as our index pattern so all data index-raw-* as well as index-hourly-* will come at a particular moment which is impacting the dashboard .
so what we are trying to achieve is if just before the deletion of index based on the age we will convert that to index-hourly-* but in transform job there is no way to provide dyanmic date in data_selection_query based on the index age
What solution would you like?
first is we can give transform job as action in ism policy so that job will run based on index age
other possible way is in data_selection_query we can have based on index age which could be fetch from ism policy somehow any variable like which is not fixed .
What alternatives have you considered?
There were a workaround provided by anthony like re-PUT of transfrom job json whenever there is change in the retension age