# Why should we not use Metricbeat with scope: node for clusters with dedicated master nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [November 8, 2023, 2:28pm UTC](https://discuss.elastic.co/t/why-should-we-not-use-metricbeat-with-scope-node-for-clusters-with-dedicated-master-nodes/346715 "2023-11-08T14:28:05Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![bunste](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bunste/32/95865_2.png) [@bunste](https://discuss.elastic.co/u/bunste)\ **Post date:** [November 8, 2023, 2:28pm UTC](https://discuss.elastic.co/t/why-should-we-not-use-metricbeat-with-scope-node-for-clusters-with-dedicated-master-nodes/346715/1 "2023-11-08T14:28:06Z")
I am currently reading the documentation on [collecting Elasticsearch monitoring data with Metricbeat](https://www.elastic.co/guide/en/elasticsearch/reference/8.11/configuring-metricbeat.html). I had already posted something about this [here in the forum](https://discuss.elastic.co/t/monitoring-an-elasticsearch-cluster-with-a-single-metricbeat-instance/311399), which led to [this issue](https://github.com/elastic/kibana/issues/139338). The documentation has improved somewhat in the meantime, but I still wonder why the `scope: node` should not be used if you have dedicated master nodes. > Metricbeat with `scope: node` collects most of the metrics from the elected master of the cluster, so you must scale up all your master-eligible nodes to account for this extra load and you should not use this mode if you have dedicated master nodes. The first part of the sentence makes sense to me: Certain metrics are only loaded from the elected master node to avoid unnecessary duplication. This works via the `ShouldSkipFetch` method in [metricbeat/module/elasticsearch/metricset.go](https://github.com/elastic/beats/blob/main/metricbeat/module/elasticsearch/metricset.go#L141). But what does the second part of the sentence > and you should not use this mode if you have dedicated master nodes. have to do with it? Why shouldn't you use this method if you have dedicated master nodes? Unfortunately, this is not explained at all. Does anyone have more information on this? The fact is that our cluster has dedicated master nodes. So does this mean that running a Metricbeat instance with `scope: node` on each node is not an option? Or is the documentation misleading or even wrong on this point? --- _[View the full topic](https://discuss.elastic.co/t/why-should-we-not-use-metricbeat-with-scope-node-for-clusters-with-dedicated-master-nodes/346715)._