# Metricbeat 8.2.2 / kibana 8.2.2 All nodes marked as master on kibana's monitoring section **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-monitoring\ **Created:** [June 13, 2022, 2:06pm UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043 "2022-06-13T14:06:22Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Roberto\_D\_Arco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roberto_d_arco/32/98729_2.png) [@Roberto\_D\_Arco](https://discuss.elastic.co/u/Roberto_D_Arco)\ **Post date:** [June 13, 2022, 2:06pm UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043/1 "2022-06-13T14:06:22Z")
It took me a while to make monitoring with metricbeat working again after the upgrade from 7.17.4 to 8.2.2 (I had to manually delete old .monitoring\* indices). Anyway, as soon as monitoring started working in Kibana, all 6 nodes of my cluster are marked as master (starred). In this cluster, all nodes can be master (all carry data). There was a similar issue before: > > > Fixes #126557 > > The Metricbeat documents always contain the field \`master\` but …the code only checked for existence of the field, not whether it was true or false. > > https://www.elastic.co/guide/en/beats/metricbeat/current/exported-fields-elasticsearch.html (search for elasticsearch.node.master) Maybe a regression? ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [June 13, 2022, 3:05pm UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043/2 "2022-06-13T15:05:32Z")
Same for me, mostly just commenting to follow ---
**Author:** ![Roberto\_D\_Arco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roberto_d_arco/32/98729_2.png) [@Roberto\_D\_Arco](https://discuss.elastic.co/u/Roberto_D_Arco)\ **Post date:** [June 16, 2022, 2:12pm UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043/3 "2022-06-16T14:12:42Z")
The linked issue has a label "v8.3.0", so I assume it will be released with that version. ---
**Author:** ![Roberto\_D\_Arco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roberto_d_arco/32/98729_2.png) [@Roberto\_D\_Arco](https://discuss.elastic.co/u/Roberto_D_Arco)\ **Post date:** [July 1, 2022, 1:56pm UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043/4 "2022-07-01T13:56:03Z")
Upgraded to ES 8.3.1 the issue is gone. ---
**Author:** ![matschaffer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matschaffer/32/95396_2.png) [@matschaffer](https://discuss.elastic.co/u/matschaffer)\ **Post date:** [July 4, 2022, 7:02am UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043/5 "2022-07-04T07:02:55Z")
Nice work, folks! 🧡 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 1, 2022, 7:03am UTC](https://discuss.elastic.co/t/metricbeat-8-2-2-kibana-8-2-2-all-nodes-marked-as-master-on-kibanas-monitoring-section/307043/6 "2022-08-01T07:03:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.