Skip to content

Commit 91eeb3a

Browse files
committed
[DOCS] Updates Kibana setup step
1 parent ea8f0f7 commit 91eeb3a

File tree

1 file changed

+22
-6
lines changed

1 file changed

+22
-6
lines changed

docs/en/stack/monitoring/esms.asciidoc

Lines changed: 22 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,14 @@ Elastic support team.
119119

120120
. {metricbeat-ref}/metricbeat-starting.html[Start {metricbeat}].
121121

122+
. Verify that your monitoring data exists in ESMS.
123+
+
124+
--
125+
Open {kib} in your web browser. Use the {kib} URL and the administrator user ID
126+
that was provided to you by the Elastic support team. Add an
127+
{kibana-ref}/index-patterns.html[index pattern] and
128+
{kibana-ref}/discover.html[explore] your monitoring data.
129+
--
122130
////
123131
To use collectors and exporters:
124132
@@ -159,7 +167,7 @@ Alternatively, you can put those settings in the `elasticsearch.yml` file on
159167
each node. This method, however, requires you to restart each node.
160168
--
161169
////
162-
////
170+
163171
[discrete]
164172
[[esms-kibana]]
165173
=== Collecting monitoring data about {kib}
@@ -223,10 +231,11 @@ You must specify the following settings in the `modules.d/kibana.yml` file:
223231
metricsets:
224232
- stats
225233
period: 10s
226-
hosts: ["http://localhost:5601"] <1>
234+
hosts: ["KIBANA_URL"] <1>
227235
xpack.enabled: true <2>
228236
----------------------------------
229-
<1> This setting identifies the host and port number that are used to access {kib}.
237+
<1> This setting identifies the host and port number that you use to access
238+
{kib}. For example, `http://localhost:5601`.
230239
<2> This setting ensures that {kib} can read the monitoring data successfully.
231240
That is to say, it's stored in the same location and format as monitoring data
232241
that is sent by {ref}/es-monitoring-exporters.html[exporters].
@@ -261,8 +270,8 @@ via HTTPS. For example, use a `hosts` setting like
261270
`https://localhost:5601` in the `modules.d/kibana.yml` file.
262271

263272
. Identify where to send the {kib} monitoring data and supply the necessary
264-
security information. Add the following settings in the {metricbeat}
265-
configuration file (`metricbeat.yml`):
273+
security information. If you have not already done so, add the following
274+
settings in the {metricbeat} configuration file (`metricbeat.yml`):
266275
+
267276
--
268277
[source,yaml]
@@ -281,7 +290,14 @@ configuration file (`metricbeat.yml`):
281290

282291
. {metricbeat-ref}/metricbeat-starting.html[Start {metricbeat}].
283292

284-
////
293+
. Verify that your monitoring data exists in ESMS.
294+
+
295+
--
296+
Open {kib} in your web browser. Use the {kib} URL and the administrator user ID
297+
that was provided to you by the Elastic support team. If it doesn't already
298+
exist, add an {kibana-ref}/index-patterns.html[index pattern] and
299+
{kibana-ref}/discover.html[explore] your monitoring data.
300+
--
285301
////
286302
To use HTTP exporters:
287303
TBD

0 commit comments

Comments
 (0)