kibana/docs/management/managing-remote-clusters.asciidoc
Kaarina Tungseth 896b9cddbc
[DOCS] Updates for navigation redesign (#68709)
* [DOCS] Updates for navigation redesign

* Getting started

* Set up text

* Discover

* Dashboard, Graph, ML, Maps, APM, SIEM, Dev tools

* Dev Tools, Stack Monitoring, Management

* Management

* Final changes

* [DOCS] Updates for navigation redesign

* [DOCS] Updates CCR monitoring screenshots

* updates SIEM screenshot and Cases overview text

* Added Brandon's APM image

* [DOCS] Refines CCR shard screenshot

* Removed merge conflict image file

Co-authored-by: lcawl <lcawley@elastic.co>
Co-authored-by: Ben Skelker <ben.skelker@elastic.co>
2020-06-12 09:39:36 -05:00

44 lines
1.8 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

[[working-remote-clusters]]
== Remote Clusters
Use *Remote Clusters* to establish a unidirectional
connection from your cluster to other clusters. This functionality is
required for {ref}/xpack-ccr.html[cross-cluster replication] and
{ref}/modules-cross-cluster-search.html[cross-cluster search].
To get started, open the menu, then go to *Stack Management > {es} > Remote Clusters*.
[role="screenshot"]
image::images/remote-clusters-list-view.png[Remote Clusters list view, including Add a remote cluster button]
[float]
[[managing-remote-clusters]]
=== Add a remote cluster
A {ref}/modules-remote-clusters.html[remote cluster] connection works by configuring a remote cluster and
connecting to a limited number of nodes, called {ref}/modules-remote-clusters.html#sniff-mode[seed nodes],
in that cluster.
Alternatively, you can define a single proxy address for the remote cluster.
By default, a cross-cluster request, such as a cross-cluster search or
replication request, fails if any cluster in the request is unavailable.
To skip a cluster when its unavailable,
set *Skip if unavailable* to true.
Once you add a remote cluster, you can configure <<managing-cross-cluster-replication, cross-cluster replication>>
to reproduce indices in the remote cluster on a local cluster.
[role="screenshot"]
image::images/add_remote_cluster.png[][UI for adding a remote cluster]
To create an index pattern to search across clusters,
use the same syntax that youd use in a raw cross-cluster search request in {es}: <cluster-names>:<pattern>.
See <<management-cross-cluster-search, Creating an index pattern>> for examples.
[float]
[[manage-remote-clusters]]
=== Manage remote clusters
From the *Remote Clusters* list view, you can drill down into each cluster and
view its status. You can also edit and delete a cluster.