From c995e73c6d5acaa6cf4b2ae3234faeee342733fb Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Tue, 22 Sep 2020 09:35:18 -0700 Subject: [PATCH] [DOCS] Add realm limitations for monitoring clusters (#62714) --- docs/reference/monitoring/production.asciidoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/reference/monitoring/production.asciidoc b/docs/reference/monitoring/production.asciidoc index b295f5c8f3d..a05003b65d9 100644 --- a/docs/reference/monitoring/production.asciidoc +++ b/docs/reference/monitoring/production.asciidoc @@ -126,6 +126,15 @@ cluster. . (Optional) Create a dedicated {kib} instance for monitoring, rather than using a single {kib} instance to access both your production cluster and monitoring cluster. ++ +-- +NOTE: If you log in to {kib} using SAML, Kerberos, PKI, OpenID Connect, or token +authentication providers, a dedicated {kib} instance is *required*. The security +tokens that are used in these contexts are cluster-specific, therefore you +cannot use a single {kib} instance to connect to both production and monitoring +clusters. + +-- .. (Optional) Disable the collection of monitoring data in this {kib} instance. Set the `xpack.monitoring.kibana.collection.enabled` setting to `false` in the