diff --git a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md index b0ff672b93..a4acffb06c 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md @@ -1,4 +1,5 @@ --- +navigation_title: Deployment mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-deployment-view.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-hosted --- -# Deployment [ec-autoops-deployment-view] +# Deployment view in AutoOps [ec-autoops-deployment-view] The **Deployment** view is the event control panel that allows you to see which issues are affecting the {{es}} cluster and get a list of action items to address them. diff --git a/deploy-manage/monitor/autoops/ec-autoops-index-view.md b/deploy-manage/monitor/autoops/ec-autoops-index-view.md index 036a84b72a..5607c64b15 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-index-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-index-view.md @@ -1,4 +1,5 @@ --- +navigation_title: Indices mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-index-view.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-hosted --- -# Indices [ec-autoops-index-view] +# Indices view in AutoOps [ec-autoops-index-view] The **Indices** view provides detailed statistics for each {{es}} index in your deployment. diff --git a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md index 843565271d..ec0a02bb24 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md @@ -1,4 +1,5 @@ --- +navigation_title: Nodes mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-nodes-view.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-hosted --- -# Nodes [ec-autoops-nodes-view] +# Nodes view in AutoOps [ec-autoops-nodes-view] The **Nodes** view provides a thorough overview on the essential metrics for all monitored deployment nodes. You can delve into specific nodes to observe metrics over extended periods. This includes data on the indexing rate and latency, search rate and latency, as well as details concerning thread pools, data, circuit breakers, network, disk, and additional elements. diff --git a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md index a7c888df82..57c0188b5c 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md @@ -1,4 +1,5 @@ --- +navigation_title: Overview mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-overview-view.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-hosted --- -# Overview [ec-autoops-overview-view] +# Overview in AutoOps [ec-autoops-overview-view] The **Overview** page displays the current status of customer deployments in {{ech}} that are linked to the same Elastic organization. diff --git a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md index e4b1f54407..6592a4d2f3 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md @@ -1,4 +1,5 @@ --- +navigation_title: Shards mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-shards-view.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-hosted --- -# Shards [ec-autoops-shards-view] +# Shards view in AutoOps [ec-autoops-shards-view] The **Shards** view allows you to manage and monitor shards allocated to each node, ensuring optimal performance and reliability of your search and indexing operations. diff --git a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md index 64d824f05b..5771d4f4c9 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md +++ b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md @@ -1,4 +1,5 @@ --- +navigation_title: Template Optimizer mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-template-optimizer.html applies_to: @@ -8,9 +9,9 @@ products: - id: cloud-hosted --- -# Template Optimizer [ec-autoops-template-optimizer] +# Template Optimizer view in AutoOps [ec-autoops-template-optimizer] -The **Template Optimizer View** offers detailed recommendations for optimizing templates. +The **Template Optimizer** view offers detailed recommendations for optimizing templates. :::{image} /deploy-manage/images/cloud-autoops-template-optimizer.png :alt: The Template Optimizer view diff --git a/deploy-manage/monitor/autoops/views.md b/deploy-manage/monitor/autoops/views.md index 5de5be0656..fdaad129f2 100644 --- a/deploy-manage/monitor/autoops/views.md +++ b/deploy-manage/monitor/autoops/views.md @@ -9,9 +9,9 @@ navigation_title: Views AutoOps offers the following views to gain further insight into difference facets of your deployment: -* [](/deploy-manage/monitor/autoops/ec-autoops-overview-view.md) -* [](/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md) -* [](/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md) -* [](/deploy-manage/monitor/autoops/ec-autoops-index-view.md) -* [](/deploy-manage/monitor/autoops/ec-autoops-shards-view.md) -* [](/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md) \ No newline at end of file +* [Overview](/deploy-manage/monitor/autoops/ec-autoops-overview-view.md) +* [Deployment](/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md) +* [Nodes](/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md) +* [Indices](/deploy-manage/monitor/autoops/ec-autoops-index-view.md) +* [Shards](/deploy-manage/monitor/autoops/ec-autoops-shards-view.md) +* [Template Optimizer](/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md) \ No newline at end of file diff --git a/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md b/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md index 0791c58e0c..5af485d728 100644 --- a/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md +++ b/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md @@ -1,4 +1,5 @@ --- +navigation_title: Examples mapped_pages: - https://www.elastic.co/guide/en/kibana/current/log-settings-examples.html applies_to: @@ -8,7 +9,7 @@ products: - id: kibana --- -# Examples [log-settings-examples] +# Examples of {{kib}} logging configurations [log-settings-examples] Here are some configuration examples for the most common logging use cases: diff --git a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md index 246dcb1275..287f02aa0c 100644 --- a/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md +++ b/deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md @@ -1,4 +1,5 @@ --- +navigation_title: Manage trusted environments mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-edit-remove-trusted-environment.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-hosted --- -# Edit or remove a trusted environment [ec-edit-remove-trusted-environment] +# Manage trusted environments for remote connections in {{ech}} [ec-edit-remove-trusted-environment] From a deployment’s **Security** page, you can manage trusted environments that were created previously. This can happen when: @@ -22,7 +23,7 @@ From a deployment’s **Security** page, you can manage trusted environments tha By removing a trusted environment, this deployment will no longer be able to establish remote connections using certificate trust to clusters of that environment. The remote environment will also no longer be able to connect to this deployment using certificate trust. ::::{note} -With this method, you can only remove trusted environments relying exclusively on certificates. To remove remote connections that use API keys for authentication, refer to [Update the access level of a remote cluster connection relying on a cross-cluster API key](#ec-edit-remove-trusted-environment-api-key). +With this method, you can only remove trusted environments relying exclusively on certificates. To remove remote connections that use API keys for authentication, refer to [Change a cross-cluster API key used for a remote connection](#ec-edit-remove-trusted-environment-api-key). :::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md index 632b46b163..857f951bcc 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-ece.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-ece.md @@ -77,7 +77,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). :::: @@ -121,7 +121,7 @@ If you later need to update the remote connection with different permissions, yo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). :::: :::::: diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md index 99f46b9d86..1831305b9a 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md @@ -77,7 +77,7 @@ The API key created previously will be used by the local deployment to authentic :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). :::::: ::::::{tab-item} TLS certificate (deprecated) diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md index eb572b1de4..32413c8f20 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md @@ -77,7 +77,7 @@ The API key created previously will be used by the local deployment to authentic :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). :::::: ::::::{tab-item} TLS certificate (deprecated) diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md index 99e85905a9..b4cfe82dea 100644 --- a/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md @@ -77,7 +77,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). :::: @@ -111,7 +111,7 @@ If you later need to update the remote connection with different permissions, yo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ec-edit-remove-trusted-environment.md#ec-edit-remove-trusted-environment-api-key). :::: :::::: diff --git a/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md b/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md index 2400457cc5..6215fa4767 100644 --- a/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md +++ b/deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md @@ -1,4 +1,5 @@ --- +navigation_title: Manage trusted environments mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-edit-remove-trusted-environment.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-enterprise --- -# Edit or remove a trusted environment [ece-edit-remove-trusted-environment] +# Manage trusted environments for remote connections in {{ece}} [ece-edit-remove-trusted-environment] From a deployment’s **Security** page, you can manage trusted environments that were created previously. This can happen when: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md index bc50512d11..b55f74b16a 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md @@ -74,7 +74,7 @@ The API key created previously will be used by the local deployment to authentic :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). :::::: ::::::{tab-item} TLS certificate (deprecated) diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md index 6b6d3cda8f..c9a6313018 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md @@ -75,7 +75,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). :::: @@ -119,7 +119,7 @@ If you later need to update the remote connection with different permissions, yo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). :::: :::::: diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md index 1802f79ea5..2cee8885c7 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md @@ -73,7 +73,7 @@ The API key created previously will be used by the local deployment to authentic :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). :::::: ::::::{tab-item} TLS certificate (deprecated) diff --git a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md index 6f35067feb..606de4962f 100644 --- a/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md +++ b/deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md @@ -77,7 +77,7 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). :::: @@ -111,7 +111,7 @@ If you later need to update the remote connection with different permissions, yo :::: -If you later need to update the remote connection with different permissions, you can replace the API key as detailed in [Update the access level of a remote cluster connection relying on a cross-cluster API key](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). +If you need to update the remote connection with different permissions later, refer to [Change a cross-cluster API key used for a remote connection](ece-edit-remove-trusted-environment.md#ece-edit-remove-trusted-environment-api-key). :::: :::::: diff --git a/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back.md b/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back.md index abc59b79b7..f948e053b2 100644 --- a/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back.md +++ b/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back.md @@ -1,4 +1,5 @@ --- +navigation_title: Failback when clusterA comes back mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/_failback_when_clustera_comes_back.html applies_to: @@ -11,7 +12,7 @@ products: - id: elasticsearch --- -# Failback when clusterA comes back [_failback_when_clustera_comes_back] +# Uni-directional recovery: failback when clusterA comes back [_failback_when_clustera_comes_back] When `clusterA` comes back, `clusterB` becomes the new leader and `clusterA` becomes the follower. diff --git a/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back_2.md b/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back_2.md index a410f06f5f..13d64bfa3c 100644 --- a/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back_2.md +++ b/deploy-manage/tools/cross-cluster-replication/_failback_when_clustera_comes_back_2.md @@ -1,4 +1,5 @@ --- +navigation_title: Failback when clusterA comes back mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/_failback_when_clustera_comes_back_2.html applies_to: @@ -11,7 +12,7 @@ products: - id: elasticsearch --- -# Failback when clusterA comes back [_failback_when_clustera_comes_back_2] +# Bi-directional recovery: Failback when clusterA comes back [_failback_when_clustera_comes_back_2] 1. You can simulate this by turning `cluster A` back on. 2. Data ingested to `cluster B` during `cluster A` 's downtime will be automatically replicated. diff --git a/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down.md b/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down.md index 1caaf5845f..c318bb024e 100644 --- a/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down.md +++ b/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down.md @@ -1,4 +1,5 @@ --- +navigation_title: Failover when clusterA is down mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/_failover_when_clustera_is_down.html applies_to: @@ -11,7 +12,7 @@ products: - id: elasticsearch --- -# Failover when clusterA is down [_failover_when_clustera_is_down] +# Uni-directional recovery: failover when clusterA is down [_failover_when_clustera_is_down] 1. Promote the follower indices in `clusterB` into regular indices so that they accept writes. This can be achieved by: diff --git a/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down_2.md b/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down_2.md index b3f9313b0a..c02e40fe6f 100644 --- a/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down_2.md +++ b/deploy-manage/tools/cross-cluster-replication/_failover_when_clustera_is_down_2.md @@ -1,4 +1,5 @@ --- +navigation_title: Failover when clusterA is down mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/_failover_when_clustera_is_down_2.html applies_to: @@ -11,7 +12,7 @@ products: - id: elasticsearch --- -# Failover when clusterA is down [_failover_when_clustera_is_down_2] +# Bi-directional recovery: Failover when clusterA is down [_failover_when_clustera_is_down_2] 1. You can simulate this by shutting down either of the clusters. Let’s shut down `cluster A` in this tutorial. 2. Start {{ls}} with the same configuration file. (This step is not required in real use cases where {{ls}} ingests continuously.)