When the ILM rolls over a new index, the monitoring for the remote cluster is lost for a short period of time. I can't find any solution for this online and no-one else seems to encounter this.
It looks like this:
This happens exactly when the Lifecycle Policy decides its time for the shards to move from the 'hot' nodes to 'warm' nodes.
Thanks