maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[DOCS] Fix monitoring links

Browse source
This commit is contained in:
lcawl 2018-11-26 13:57:34 -08:00
parent e082471ee8
commit 4c43f12cfb
2 changed files with 8 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/monitoring/configuring-monitoring.asciidoc
View file

@ -5,17 +5,14 @@
<titleabbrev>Configuring monitoring</titleabbrev>
++++
If you enable the Elastic {monitor-features} in your cluster, you can
optionally collect metrics about {kib}:
If you enable the {monitor-features} in your cluster, there are two methods to
collect metrics about {kib}:
* <<monitoring-kibana>>
* <<monitoring-metricbeat>>
You can also use {kib} to visualize
monitoring data from across the {stack}:
* <<monitoring-data>>
You can also use {kib} to
<<monitoring-data,visualize monitoring data from across the {stack}>>.
To learn about monitoring in general, see
{stack-ov}/xpack-monitoring.html[Monitoring the {stack}].

7
docs/monitoring/index.asciidoc
View file

@ -9,9 +9,7 @@ The {kib} {monitor-features} serve two separate purposes:
. To visualize monitoring data from across the {stack}. You can view health and
performance data for {es}, {ls}, and Beats in real time, as well as analyze past
performance. For more information, see
{stack-ov}/xpack-monitoring.html[Monitoring the {stack}].
performance.
. To monitor {kib} itself and route that data to the monitoring cluster.
If you enable monitoring across the {stack}, each {es} node, {ls} node, {kib}
@ -22,6 +20,9 @@ or instance starts.
NOTE: Watcher must be enabled to view cluster alerts. If you have a Basic
license, Top Cluster Alerts are not displayed.
For more information, see <<configuring-monitoring>> and
{stack-ov}/xpack-monitoring.html[Monitoring the {stack}].
--
include::beats-details.asciidoc[]