[DOCS] Updates remote cluster and ccr docs #63517
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gchaps
added
Team:Docs
v8.0.0
release_note:skip
|
Pinging @elastic/kibana-docs (Team:Docs) |
KOTungseth
reviewed
Apr 16, 2020
| clusters and managing the {ccr} process. You can replicate indices from a | ||
| leader remote cluster to a follower index in a local cluster. The local follower indices | ||
| can be used to provide remote backups for disaster recovery or for geo-proximite copies of data. | ||
| Use *Remote Clusters* to establish a uni-directional |
There was a problem hiding this comment.
It is more common to use unidirectional than uni-directional. Also, do our users know what unidirectional means? Couldn't you just say to establish a single direct connection from your cluster to other clusters?
|
|
||
| Replication requires a leader index, the index being replicated, and a | ||
| follower index, which will contain the leader index's replicated data. | ||
| The follower index is passive in that it can serve read requests and searches, |
|
|
||
| To automatically detect and follow new indices when they are created on a remote cluster, | ||
| go to *Auto-follow patterns*. Creating an auto-follow pattern is useful when you have | ||
| time-series data, like event logs, on the remote cluster that is created or rolled over on a daily basis. |
There was a problem hiding this comment.
time-series > time series
| [[manage-replication]] | ||
| === Manage replication | ||
|
|
||
| Use the list views in *Cross-cluster replication* to monitor whether the replication is active and |
There was a problem hiding this comment.
*Cross-cluster replication* > *Cross-Cluster Replication*
| [[manage-replication]] | ||
| === Manage replication | ||
|
|
||
| Use the list views in *Cross-cluster replication* to monitor whether the replication is active and |
There was a problem hiding this comment.
the replication is active and pause and resume replication. > the replication is active, and pause and resume replication.
| pause and resume replication. You can also edit and remove the follower indices and auto-follow patterns. | ||
|
|
||
|
|
||
| [float] |
There was a problem hiding this comment.
I would remove lines 74 thru 76, then replace with:
For an example of cross-cluster replication, refer to https://www.elastic.co/blog/bi-directional-replication-with-elasticsearch-cross-cluster-replication-ccr[Bi-directional replication with Elasticsearch cross-cluster replication].
The single bullet looks a bit rogue.
docs/user/management.asciidoc
Outdated
| @@ -85,7 +85,7 @@ set the timespan for notification messages, and much more. | |||
|
|
|||
| | <<managing-alerts-and-actions, *Alerts and Actions*>> | |||
|
|
|||
| Centrally manage your alerts from across {kib}. Create and manage re-usable connectors for triggering actions. | |||
| Centrally manage your alerts from across {kib}. Create and manage re-usable connectors for triggering actions. | |||
There was a problem hiding this comment.
from across {kib} > across {kib}
gchaps
added a commit
to gchaps/kibana
that referenced
this pull request
Apr 16, 2020
* [DOCS] Updates remote cluster and ccr docs * [DOCS] Adds section on managing clusters and follower indices * [DOCS] Incorporates review comments
gchaps
added a commit
to gchaps/kibana
that referenced
this pull request
Apr 16, 2020
* [DOCS] Updates remote cluster and ccr docs * [DOCS] Adds section on managing clusters and follower indices * [DOCS] Incorporates review comments
gchaps
added a commit
that referenced
this pull request
Apr 16, 2020
gchaps
added a commit
that referenced
this pull request
Apr 16, 2020
gmmorris
added a commit
to gmmorris/kibana
that referenced
this pull request
Apr 17, 2020
* master: (40 commits) [APM]Upgrade apm-rum agent to latest version to fix full page reload (elastic#63723) add deprecation warning for legacy 3rd party plugins (elastic#62401) Migrate timelion vis (elastic#62819) Replacebad scope link with actual values (elastic#63444) Index pattern management UI -> TypeScript and New Platform Ready (create_index_pattern_wizard) (elastic#63111) [SIEM] Threat hunting enhancements: Filter for/out value, Show top field, Copy to Clipboard, Draggable chart legends (elastic#61207) [Maps] fix term join agg key collision (elastic#63324) [Ingest] Fix agent config key sorting (elastic#63488) [Monitoring] Fixed server response errors (elastic#63181) update elastic charts to 18.3.0 (elastic#63732) Start services (elastic#63720) [APM] Encode spaces when creating ML job (elastic#63683) Uptime 7.7 docs (elastic#62228) [DOCS] Updates remote cluster and ccr docs (elastic#63517) [Maps] Add 3rd party vector tile support (elastic#62084) [Endpoint][EPM] Retrieve Index Pattern from Ingest Manager (elastic#63016) [Endpoint] Host Details Policy Response Panel (elastic#63518) [Uptime] Certificate expiration threshold settings (elastic#63682) Refactor saved object types to use `namespaceType` (elastic#63217) [SIEM][CASE] Create comments sequentially (elastic#63692) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR divides the Remote Clusters and CCR docs into two separate docs and updates them for 7.7.
Checklist
Delete any items that are not applicable to this PR.