Skip to content

Commit

Permalink
[DOCS] Fixes typo
Browse files Browse the repository at this point in the history
  • Loading branch information
lcawl committed May 24, 2019
1 parent 9a64db1 commit 99937d1
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions docs/en/stack/monitoring/esms.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ For more information, see

. {kibana-ref}/start-stop.html[Start {kib}].

. Ensure that the `xpack.monitoring.collection.enabled` setting to `true` on
. Ensure that the `xpack.monitoring.collection.enabled` setting is `true` on
each node in the production cluster.

. {metricbeat-ref}/metricbeat-installation.html[Install {metricbeat}] on the
Expand All @@ -209,19 +209,21 @@ include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=enable-kib
include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=configure-kibana-module]
--

. If the {stack} {security-features} are enabled, you must also provide a user
. If the {stack} {security-features} are enabled, you must also provide a user
ID and password so that {metricbeat} can collect metrics successfully.

+
--
include::{kib-repo-dir}/monitoring/monitoring-metricbeat.asciidoc[tag=remote-monitoring-user]
--

. If you configured {kib} to use
{kibana-ref}/configuring-tls.html[encrypted communications], you must access it
via HTTPS. For example, use a `hosts` setting like
`https://localhost:5601` in the `modules.d/kibana-xpack.yml` file.

. Identify where to send the {kib} monitoring data and supply the necessary
security information. If you have not already done so, add the following
settings in the {metricbeat} configuration file (`metricbeat.yml`):
security information. Add the following settings in the {metricbeat}
configuration file (`metricbeat.yml`):
+
--
[source,yaml]
Expand Down

0 comments on commit 99937d1

Please sign in to comment.