maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[DOC] Clarify supported realms when accessing remote monitoring clusters (#77938)

Browse source 
Co-authored-by: lcawl <lcawley@elastic.co>
This commit is contained in:
Luca Belluccini 2020-09-22 18:44:30 +02:00 committed by GitHub
parent d666038c8f
commit 0238206ace
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/user/monitoring/viewing-metrics.asciidoc
View file

@ -13,13 +13,19 @@ At a minimum, you must have monitoring data for the {es} production cluster.
Once that data exists, {kib} can display monitoring data for other products in
the cluster.
TIP: If you use a separate monitoring cluster to store the monitoring data, it
is strongly recommended that you use a separate {kib} instance to view it. 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. For more information about the recommended configuration, see
{ref}/monitoring-overview.html[Monitoring overview].
. Identify where to retrieve monitoring data from.
+
--
The cluster that contains the monitoring data is referred to
as the _monitoring cluster_.
TIP: If the monitoring data is stored on a *dedicated* monitoring cluster, it is
If the monitoring data is stored on a dedicated monitoring cluster, it is
accessible even when the cluster you're monitoring is not. If you have at least
a gold license, you can send data from multiple clusters to the same monitoring
cluster and view them all through the same instance of {kib}.