[Monitoring LS] Recommends collecting metricsets to fully visualize metrics on dashboards. (#17479)

* Disabling some of metricsets may cause dashboards partially display some metrics. This change recommends collecting metricsets to fully visualize metrics on dashboards.

* Paraphrasing sentences and grammar correction.

Co-authored-by: Rob Bavey <rob.bavey@elastic.co>

* Update docs/reference/serverless-monitoring-with-elastic-agent.md

* Make recommendation as a tip.

---------

Co-authored-by: Rob Bavey <rob.bavey@elastic.co>

docs/reference/dashboard-monitoring-with-elastic-agent.md

@@ -85,6 +85,10 @@ Check out [Installing {{agent}}](docs-content://reference/fleet/install-elastic-
 
 6. Configure the integration to collect metrics.
 
+    ::::{tip}
+    For the best experience with the {{ls}} dashboards, we recommend collecting all of the metrics. Turning off metrics will result in incomplete or missing visualizations.
+    ::::
+
     * Make sure that **Metrics (Elastic Agent)** is turned on (default), and **Metrics (Stack Monitoring)** is turned off.
     * Under **Metrics (Elastic Agent)**, make sure the {{ls}} URL setting points to your {{ls}} instance URLs.<br> By default, the integration collects {{ls}} monitoring metrics from `https://localhost:9600`. If that host and port number are not correct, update the `Logstash URL` setting. If you configured {{ls}} to use encrypted communications and/or a username and password, you must access it via HTTPS, and expand the **Advanced Settings** options, and fill in with the appropriate values for your {{ls}} instance.
 

docs/reference/monitoring-with-elastic-agent.md

@@ -92,6 +92,10 @@ Check out [Installing {{agent}}](docs-content://reference/fleet/install-elastic-
 
 6. Configure the integration to collect metrics
 
+    ::::{tip}
+    For the best experience with Stack Monitoring, we recommend collecting both `node` and `node_stats`. Turning off either of these will result in incomplete or missing visualizations.
+    ::::
+
     * Make sure that **Metrics (Stack Monitoring)** is turned on, and **Metrics (Elastic Agent)** is turned off, if you want to collect metrics from your {{ls}} instance.
     * Under **Metrics (Stack Monitoring)**, make sure the hosts setting points to your {{ls}} host URLs. By default, the integration collects {{ls}} monitoring metrics from `localhost:9600`. If that host and port number are not correct, update the `hosts` setting. If you configured {{ls}} to use encrypted communications, you must access it via HTTPS. For example, use a `hosts` setting like `https://localhost:9600`.
 

docs/reference/monitoring-with-metricbeat.md

@@ -85,7 +85,11 @@ Refer to [{{es}} cluster stats page](https://www.elastic.co/docs/api/doc/elastic
         xpack.enabled: true
     ```
 
-    Set the `hosts`, `username`, and `password` to authenticate with {{ls}}. For other module settings, it’s recommended that you accept the defaults.
+   ::::{tip}
+   For the best experience with Stack Monitoring, we recommend collecting both `node` and `node_stats` metricsets. Turning off either of these will result in incomplete or missing visualizations.
+   ::::
+
+    Set the `hosts`, `username`, and `password` to authenticate with {{ls}}.
 
     By default, the module collects {{ls}} monitoring data from `localhost:9600`.
 

docs/reference/serverless-monitoring-with-elastic-agent.md

@@ -46,6 +46,10 @@ For more info, check out the [Elastic Observability](docs-content://solutions/ob
 
 **Configure the integration to collect metrics**
 
+::::{tip}
+For the best experience with the Logstash dashboards, we recommend collecting all of the metrics. Turning off metrics will result in incomplete or missing visualizations.
+::::
+
 * Make sure that **Metrics (Elastic Agent)** is turned on (default), and **Metrics (Stack Monitoring)** is turned off.
 * Set the {{ls}} URL to point to your {{ls}} instance.<br> By default, the integration collects {{ls}} monitoring metrics from `https://localhost:9600`. If that host and port number are not correct, update the `Logstash URL` setting. If you configured {{ls}} to use encrypted communications and/or a username and password, you must access it using HTTPS. Expand the **Advanced Settings** options, and fill in the appropriate values for your {{ls}} instance.