[Internal]: stack monitoring configuration guide inconsistencies / bugs

[shainaraskas]

Description

From @thekofimensah in slack

I'm working on an implementation where a single elasticsearch cluster wants to be monitored by another elasticsearch instance using metricbeat.
From my troubleshooting, I used this reference and this reference.
Firstly for some feedback, the first doc somewhat suddenly ends by just saying to "send data to the cluster" without saying what you need to do to make it work. The second doc actually talks about this and it' not straight foreward. I would suggest referencing the second doc or writing it out in the first page for clarity.
Now for the second doc, there is something that I was having trouble with. It seems to me that if you use the default scope:node property and install metricbeat on all of the nodes, remote stack monitoring doesn't work. At least I wasn't able to make it work. However scope:cluster did make it work. If it's true that scope:node doesn't work for remote monitoring, I think it should explicitly say that.
The doc says:

Ideally, install a single Metricbeat instance configured with scope: cluster and configure hosts to point to an endpoint, such as a load-balancing proxy, which directs requests to the master-ineligible nodes in the cluster.
If this is not possible, then install one Metricbeat instance for each Elasticsearch node in the production cluster and use the default scope: node. When Metricbeat is monitoring Elasticsearch with scope: node then you must install a Metricbeat instance for each Elasticsearch node. If you don’t, some metrics will not be collected.
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. You should not use this mode if you have dedicated master nodes.

Resources

Which documentation set does this change impact?

Elastic On-Prem only

Feature differences

What release is this request related to?

N/A

Serverless release

Collaboration model

The documentation team

Point of contact.

Stakeholders: #stack-monitoring in slack