# Kibana data node monitoring stops after five minutes **URL:** \ **Category:** Kibana\ **Created:** [June 18, 2024, 7:45pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674 "2024-06-18T19:45:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mbby](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mbby](https://discuss.elastic.co/u/mbby)\ **Post date:** [June 18, 2024, 7:45pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/1 "2024-06-18T19:45:49Z")
I've a cluster with five nodes, running 8.4.1. One of the nodes had write rejections. We restarted the node and everything went back to a working state. But after five minutes no monitoring data was displayed anymore. If I restart the node monitoring data is coming in but after five minutes it stops again (short time after the dashboard shows 0 unassigned shards). Just to mention: we had to delete some indices today because we were nearly running out of disk space (e.g. .ds-filebeat...). It looks like the cluster is still working as expected. If I do a \_cat/nodes?v I could see the node and the data (like CPU) changes. Kibana reports 11 nodes but only shows 10 in the list. If I click on enter setup mode, the node is shown but greyed out. All nodes are marked as self monitored. Does someone know what is broken and how to fix it? ---
**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\ **Post date:** [June 18, 2024, 8:09pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/2 "2024-06-18T20:09:53Z")
Thanks for reaching out, @mbby. I have a follow up question, did you get any error messages? If, so what did they say? ---
**Author:** ![mbby](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mbby](https://discuss.elastic.co/u/mbby)\ **Post date:** [June 18, 2024, 8:36pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/3 "2024-06-18T20:36:51Z")
Yes. Just found the log. It says: failed to flush export bulks ---
**Author:** ![mbby](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mbby](https://discuss.elastic.co/u/mbby)\ **Post date:** [June 18, 2024, 8:39pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/4 "2024-06-18T20:39:29Z")
![Screenshot 2024-06-18 at 22.38.58](https://us1.discourse-cdn.com/elastic/original/3X/8/a/8ac4d2c1cd577d56431b4290fc34ea017d25a73b.png) ---
**Author:** ![mbby](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mbby](https://discuss.elastic.co/u/mbby)\ **Post date:** [June 18, 2024, 8:57pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/5 "2024-06-18T20:57:46Z")
Just seen: this node only has replicas. Don't know why. ---
**Author:** ![mbby](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mbby](https://discuss.elastic.co/u/mbby)\ **Post date:** [June 19, 2024, 4:36am UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/6 "2024-06-19T04:36:14Z")
The system recovered itself. I reduced the load. But it took some hours. ---
**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\ **Post date:** [June 19, 2024, 7:57pm UTC](https://discuss.elastic.co/t/kibana-data-node-monitoring-stops-after-five-minutes/361674/7 "2024-06-19T19:57:07Z")
Thanks for sharing your solution, @mbby.