So we recently updated our hosted Elastic Cloud deployment to 7.4.1 to resolve the issue discussed in 503 Queue is full. The fix worked so all happy there. However, I came in this morning to find the disk nearly full...how could this be?
Well. When APM is upgraded, it looks like it resets the index templates and hence reset back to the default ILM policies. In our case we've created our own policies to be much tighter on retention, etc. so this explains why I now have a single, large 7.4.1 index for transactions!
I've combed though the docs and it looks like this can be overridden but it talks about pointing to a fields.yml file. Thing is
a) I only want to override the template for the -transaction, -span, etc templates
b) How does one have this fields.yml file be referenced when using hosted Elastic Cloud?
Or am I just misunderstanding how the template gets overridden?