github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Change deep link to ES book for CCS privileges (#164165)

Browse source 
## Summary

Relates to https://github.com/elastic/elasticsearch/pull/98330

8.10 introduces a new method to configure remote clusters (API key
based), which will live next to the existing method (certificate based).
As a result, the ES remote cluster docs will be restructured. The deep
link from "[Alerting set
up](https://www.elastic.co/guide/en/kibana/current/alerting-setup.html#alerting-ccs-setup)"
to the setting up CCS privileges section in the ES docs will break (and
would potentially bring folks to the wrong page anyway).

This PR changes the link into a link to the higher-level remote cluster
docs, from where folks can click through to the section that is relevant
to them.
This commit is contained in:
Abdon Pijpelink 2023-08-22 09:33:53 +02:00 • committed by GitHub
parent 31eed021e9
commit 4b1d833aee
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/user/alerting/alerting-setup.asciidoc
View file

@ -109,5 +109,5 @@ The same behavior occurs when you change the API key in the header of your API c
[[alerting-ccs-setup]]
=== {ccs-cap}
If you want to use alerting rules with {ccs}, you must configure
{ref}/remote-clusters-privileges.html#clusters-privileges-ccs-kibana[privileges for {ccs-init} and {kib}].
If you want to use alerting rules with {ccs}, you must configure privileges for
{ccs-init} and {kib}. Refer to {ref}/remote-clusters.html[Remote clusters].