From 85351564eada523635e1a5b12dab31beb9a426cf Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Tue, 28 May 2019 14:14:57 -0700 Subject: [PATCH] Remove to-do and fix attribute resolution (#12291) --- libbeat/docs/monitoring/monitoring-beats.asciidoc | 2 +- libbeat/docs/security/users.asciidoc | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/libbeat/docs/monitoring/monitoring-beats.asciidoc b/libbeat/docs/monitoring/monitoring-beats.asciidoc index 3a85a73ab40..2015d971903 100644 --- a/libbeat/docs/monitoring/monitoring-beats.asciidoc +++ b/libbeat/docs/monitoring/monitoring-beats.asciidoc @@ -38,7 +38,7 @@ configured the {es} output and want to send {beatname_uc} monitoring events to the same {es} cluster, specify the following minimal configuration: + -- -[source, yml] +["source","yml",subs="attributes"] -------------------- xpack.monitoring: enabled: true diff --git a/libbeat/docs/security/users.asciidoc b/libbeat/docs/security/users.asciidoc index cb6b78b3f2a..92c424c20b9 100644 --- a/libbeat/docs/security/users.asciidoc +++ b/libbeat/docs/security/users.asciidoc @@ -2,8 +2,6 @@ [[feature-roles]] === Grant users access to secured resources -//TODO: Redirect beats-user-access to feature-roles to prevent 404s. - You can use role-based access control to grant users access to secured resources. The roles that you set up depend on your organization's security requirements and the minimum privileges required to use specific features.