# Monitoring disappears during a rollover \[7.1.1\]

**URL:** <https://discuss.elastic.co/t/monitoring-disappears-during-a-rollover-7-1-1/187585>\
**Category:** Kibana\
**Created:** [June 26, 2019, 1:56pm UTC](https://discuss.elastic.co/t/monitoring-disappears-during-a-rollover-7-1-1/187585 "2019-06-26T13:56:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ljefferies](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ljefferies/32/48432_2.png) [@ljefferies](https://discuss.elastic.co/u/ljefferies)\
**Post date:** [June 26, 2019, 1:56pm UTC](https://discuss.elastic.co/t/monitoring-disappears-during-a-rollover-7-1-1/187585/1 "2019-06-26T13:56:42Z")

</div>

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:

![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/44d476579552af620b6846594ef62ae90af1af00.png)

This happens exactly when the Lifecycle Policy decides its time for the shards to move from the 'hot' nodes to 'warm' nodes.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 24, 2019, 2:01pm UTC](https://discuss.elastic.co/t/monitoring-disappears-during-a-rollover-7-1-1/187585/2 "2019-07-24T14:01:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.