Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 6 commits into from
Sep 22, 2020
Merged

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

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5238e78
[DOC] Clarify supported realms when accessing remote monitoring clusters
lucabelluccini Sep 18, 2020
2dca330
[DOCS] Add tip to introduction
lcawl Sep 21, 2020
dde324b
[DOCS] More edits
lcawl Sep 21, 2020
5c2a2fc
[DOCS] Add token authentication provider detail
lcawl Sep 22, 2020
20ae5a0
[DOCS] Minor edit
lcawl Sep 22, 2020
f5b1f12
[DOCS] Remove too many admonition blocks
lcawl Sep 22, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/user/monitoring/viewing-metrics.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,15 @@ 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
the monitoring cluster uses a SAML, Kerberos, PKI, or OpenID Connect
realm, a dedicated {kib} instance is required. The security tokens that are used
in these realms are cluster-specific and therefore cannot be used by a single
{kib} instance to connect to both the 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.
+
--
Expand Down Expand Up @@ -61,6 +70,10 @@ NOTE: These users must exist on the monitoring cluster. If you are accessing a
remote monitoring cluster, you must use credentials that are valid on both the
{kib} server and the monitoring cluster.

////
NOTE: Only the file, native, reserved, LDAP and Active Directory realms authentication
realms are supported when accessing a remote monitoring cluster.
////
--

.. Create users that have the `monitoring_user` and `kibana_admin`
Expand Down