@@ -191,7 +191,7 @@ For more information, see
191
191
192
192
. {kibana-ref}/start-stop.html[Start {kib}].
193
193
194
- . Ensure that the `xpack.monitoring.collection.enabled` setting to `true` on
194
+ . Ensure that the `xpack.monitoring.collection.enabled` setting is `true` on
195
195
each node in the production cluster.
196
196
197
197
. {metricbeat-ref}/metricbeat-installation.html[Install {metricbeat}] on the
@@ -209,19 +209,21 @@ include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=enable-kib
209
209
include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=configure-kibana-module]
210
210
--
211
211
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
213
213
ID and password so that {metricbeat} can collect metrics successfully.
214
-
214
+ +
215
+ --
215
216
include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=remote-monitoring-user]
217
+ --
216
218
217
219
. If you configured {kib} to use
218
220
{kibana-ref}/configuring-tls.html[encrypted communications], you must access it
219
221
via HTTPS. For example, use a `hosts` setting like
220
222
`https://localhost:5601` in the `modules.d/kibana-xpack.yml` file.
221
223
222
224
. 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`):
225
227
+
226
228
--
227
229
[source,yaml]
0 commit comments