From 135f8b2b0787b63f2226bb710a373fde204be637 Mon Sep 17 00:00:00 2001 From: Brandon Morelli Date: Tue, 12 May 2020 09:40:54 -0700 Subject: [PATCH] docs: fix apm server links (#56551) --- .../docs/en/security/authentication/built-in-users.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/x-pack/docs/en/security/authentication/built-in-users.asciidoc b/x-pack/docs/en/security/authentication/built-in-users.asciidoc index c81565638245e..3bcd6130bb4eb 100644 --- a/x-pack/docs/en/security/authentication/built-in-users.asciidoc +++ b/x-pack/docs/en/security/authentication/built-in-users.asciidoc @@ -178,8 +178,8 @@ for these users. The `apm_system` user is used internally within APM when monitoring is enabled. -To enable this feature in APM, you need to update the -{apm-server-ref-70}/configuring-howto-apm-server.html[APM configuration file] to +To enable this feature in APM, you need to update the +{apm-server-ref-v}/configuring-howto-apm-server.html[APM configuration file] to reference the correct username and password. For example: [source,yaml] @@ -188,7 +188,7 @@ xpack.monitoring.elasticsearch.username: apm_system xpack.monitoring.elasticsearch.password: apmserverpassword ---------------------------------------------------------- -See {apm-server-ref-70}/monitoring.html[Monitoring APM Server]. +See {apm-server-ref-v}/monitoring.html[Monitoring APM Server]. If you have upgraded from an older version of {es}, then you may not have set a password for the `apm_system` user. If this is the case,