[DOCS] Fixes links to monitoring content (#11166) (#11172)

This commit is contained in:
Lisa Cawley 2019-09-30 10:19:35 -07:00 committed by GitHub
parent dfb3cb5a34
commit fc0db0d955
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions

View file

@ -10,7 +10,7 @@ To monitor Logstash nodes:
. Identify where to send monitoring data. This cluster is often referred to as
the _production cluster_. For examples of typical monitoring architectures, see
{xpack-ref}/how-monitoring-works.html[How Monitoring Works].
{ref}/how-monitoring-works.html[How monitoring works].
+
--
IMPORTANT: To visualize Logstash as part of the Elastic Stack (as shown in Step
@ -102,6 +102,6 @@ image:static/monitoring/images/monitoring-ui.png["Monitoring",link="monitoring/i
When upgrading from older versions of {xpack}, the built-in `logstash_system`
user is disabled for security reasons. To resume monitoring,
{xpack-ref}/monitoring-troubleshooting.html[change the password and re-enable the logstash_system user].
change the password and re-enable the `logstash_system` user.
include::{log-repo-dir}/static/settings/monitoring-settings.asciidoc[]

View file

@ -29,7 +29,7 @@ expected to be the production cluster. This configuration enables the production
{es} cluster to add metadata (for example, its cluster UUID) to the Logstash
monitoring data then route it to the monitoring clusters. For more information
about typical monitoring architectures, see
{xpack-ref}/how-monitoring-works.html[How Monitoring Works].
{ref}/how-monitoring-works.html[How monitoring works].
include::collectors.asciidoc[]
include::monitoring-output.asciidoc[]