Would it be possible to support the configuration of the periodicy or execution hour of clean up job which deletes old x-pack system indexes (.monitoring, etc)? Or have it run on startup as well as 01h00?
We are running some ES/x-pack clusters that are switched off outside of office hours. I think this must be a common senario for anyone using cloud hosting providers for their dev/test platforms.
As a result, the job that usually runs at 01h00 to clean up old indicies is never executed.
For now we have a curator job in place to handle what would otherwise be done automatically, which works out fine of course.