From 382baf40167349609c73dcca7c2647f8e5dda27d Mon Sep 17 00:00:00 2001 From: lcawl Date: Thu, 17 Oct 2019 14:24:14 -0700 Subject: [PATCH] Fixes links to Stack Overview Fixes #11239 --- docs/static/azure-module.asciidoc | 2 +- docs/static/deploying.asciidoc | 2 +- docs/static/monitoring/monitoring-internal.asciidoc | 2 +- docs/static/monitoring/monitoring-mb.asciidoc | 6 +++--- docs/static/security/logstash.asciidoc | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/static/azure-module.asciidoc b/docs/static/azure-module.asciidoc index 1f2028771..06c22d9e7 100644 --- a/docs/static/azure-module.asciidoc +++ b/docs/static/azure-module.asciidoc @@ -492,7 +492,7 @@ the event originated. ==== Deploying the module in production Use security best practices to secure your configuration. -See {stack-ov}/elasticsearch-security.html[Securing the {stack}] for details and recommendations. +See {ref}/secure-cluster.html[Secure a cluster] for details and recommendations. [[azure-resources]] ==== Microsoft Azure resources diff --git a/docs/static/deploying.asciidoc b/docs/static/deploying.asciidoc index 8813bd3c8..4f25da382 100644 --- a/docs/static/deploying.asciidoc +++ b/docs/static/deploying.asciidoc @@ -124,7 +124,7 @@ Enterprise-grade security is available across the entire delivery chain. * There’s a wealth of security options when communicating with Elasticsearch including basic authentication, TLS, PKI, LDAP, AD, and other custom realms. To enable Elasticsearch security, see -{stack-ov}/elasticsearch-security.html[Securing the {stack}]. +{ref}/secure-cluster.html[Secure a cluster]. [float] ==== Monitoring diff --git a/docs/static/monitoring/monitoring-internal.asciidoc b/docs/static/monitoring/monitoring-internal.asciidoc index 05773f1f7..86bfc27ec 100644 --- a/docs/static/monitoring/monitoring-internal.asciidoc +++ b/docs/static/monitoring/monitoring-internal.asciidoc @@ -58,7 +58,7 @@ is disabled in {es} and data is ignored from all other sources. . Configure your Logstash nodes to send metrics by setting the `xpack.monitoring.elasticsearch.hosts` in `logstash.yml`. If {security} is enabled, you also need to specify the credentials for the -{stack-ov}/built-in-users.html[built-in `logstash_system` user]. For more +{ref}/built-in-users.html[built-in `logstash_system` user]. For more information about these settings, see <>. + -- diff --git a/docs/static/monitoring/monitoring-mb.asciidoc b/docs/static/monitoring/monitoring-mb.asciidoc index 6281fbe5e..2272227cb 100644 --- a/docs/static/monitoring/monitoring-mb.asciidoc +++ b/docs/static/monitoring/monitoring-mb.asciidoc @@ -119,7 +119,7 @@ it using HTTPS. For example, use a `hosts` setting like `https://localhost:9600` ID and password so that {metricbeat} can collect metrics successfully: .. Create a user on the production cluster that has the -`remote_monitoring_collector` {stack-ov}/built-in-roles.html[built-in role]. +`remote_monitoring_collector` {ref}/built-in-roles.html[built-in role]. .. Add the `username` and `password` settings to the module configuration file (`logstash-xpack.yml`). @@ -180,9 +180,9 @@ must provide a valid user ID and password so that {metricbeat} can send metrics successfully: .. Create a user on the monitoring cluster that has the -`remote_monitoring_agent` {stack-ov}/built-in-roles.html[built-in role]. +`remote_monitoring_agent` {ref}/built-in-roles.html[built-in role]. Alternatively, use the `remote_monitoring_user` -{stack-ov}/built-in-users.html[built-in user]. +{ref}/built-in-users.html[built-in user]. + TIP: If you're using index lifecycle management, the remote monitoring user requires additional privileges to create and read indices. For more diff --git a/docs/static/security/logstash.asciidoc b/docs/static/security/logstash.asciidoc index 42c499196..58113c9a9 100644 --- a/docs/static/security/logstash.asciidoc +++ b/docs/static/security/logstash.asciidoc @@ -204,7 +204,7 @@ data to a secure cluster, you need to configure the username and password that Logstash uses to authenticate for shipping monitoring data. {security} comes preconfigured with a -{stack-ov}/built-in-users.html[`logstash_system` built-in user] +{ref}/built-in-users.html[`logstash_system` built-in user] for this purpose. This user has the minimum permissions necessary for the monitoring function, and _should not_ be used for any other purpose - it is specifically _not intended_ for use within a Logstash pipeline.