@@ -191,7 +191,7 @@ For more information, see
191191
192192. {kibana-ref}/start-stop.html[Start {kib}].
193193
194- . Ensure that the `xpack.monitoring.collection.enabled` setting to `true` on
194+ . Ensure that the `xpack.monitoring.collection.enabled` setting is `true` on
195195each node in the production cluster.
196196
197197. {metricbeat-ref}/metricbeat-installation.html[Install {metricbeat}] on the
@@ -209,19 +209,21 @@ include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=enable-kib
209209include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=configure-kibana-module]
210210--
211211
212- . If the {stack} {security-features} are enabled, you must also provide a user
212+ . If the {stack} {security-features} are enabled, you must also provide a user
213213ID and password so that {metricbeat} can collect metrics successfully.
214-
214+ +
215+ --
215216include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=remote-monitoring-user]
217+ --
216218
217219. If you configured {kib} to use
218220{kibana-ref}/configuring-tls.html[encrypted communications], you must access it
219221via HTTPS. For example, use a `hosts` setting like
220222`https://localhost:5601` in the `modules.d/kibana-xpack.yml` file.
221223
222224. Identify where to send the {kib} monitoring data and supply the necessary
223- security information. If you have not already done so, add the following
224- settings in the {metricbeat} configuration file (`metricbeat.yml`):
225+ security information. Add the following settings in the {metricbeat}
226+ configuration file (`metricbeat.yml`):
225227+
226228--
227229[source,yaml]
0 commit comments