diff --git a/deploy-manage/deploy/cloud-enterprise/access-kibana.md b/deploy-manage/deploy/cloud-enterprise/access-kibana.md index 2869434038..77bcdc955a 100644 --- a/deploy-manage/deploy/cloud-enterprise/access-kibana.md +++ b/deploy-manage/deploy/cloud-enterprise/access-kibana.md @@ -1,4 +1,5 @@ --- +navigation_title: Access {{kib}} mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-access-kibana.html - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-kibana.html @@ -9,7 +10,7 @@ products: - id: cloud-enterprise --- -# Access {{kib}} [ece-access-kibana] +# Access {{kib}} on {{ece}} [ece-access-kibana] {{kib}} is an open source analytics and visualization platform designed to search, view, and interact with data stored in {{es}} indices. diff --git a/deploy-manage/deploy/cloud-enterprise/add-plugins.md b/deploy-manage/deploy/cloud-enterprise/add-plugins.md index 773003eb9d..db7643b639 100644 --- a/deploy-manage/deploy/cloud-enterprise/add-plugins.md +++ b/deploy-manage/deploy/cloud-enterprise/add-plugins.md @@ -1,11 +1,11 @@ --- -navigation_title: Configure plugins and extensions +navigation_title: Add plugins and extensions applies_to: deployment: ece: --- -# Add plugins and extensions [ece-adding-plugins] +# Add plugins and extensions in {{ece}} [ece-adding-plugins] Plugins extend the core functionality of {{es}}. {{ece}} makes it easy to add plugins to your deployment by providing a number of plugins that work with your version of {{es}}. One advantage of these plugins is that you generally don’t have to worry about upgrading plugins when upgrading to a new {{es}} version, unless there are breaking changes. The plugins are upgraded along with the rest of your deployment. diff --git a/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md b/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md index 28e3f46d20..4498a13036 100644 --- a/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md +++ b/deploy-manage/deploy/cloud-enterprise/keep-track-of-deployment-activity.md @@ -1,4 +1,5 @@ --- +navigation_title: Keep track of deployment activity mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-activity-page.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-enterprise --- -# Keep track of deployment activity [ece-activity-page] +# Keep track of deployment activity on {{ece}} [ece-activity-page] The deployment **Activity** page gives you a convenient way to follow all configuration changes that have been applied to your deployment, including which resources were affected, when the changes were applied, who initiated the changes, and whether or not the changes were successful. You can also select **Details** for an expanded, step-by-step view of each change applied to each deployment resource. diff --git a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-logstash.md b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-logstash.md index 25867ab287..d915641169 100644 --- a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-logstash.md +++ b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-logstash.md @@ -1,4 +1,5 @@ --- +navigation_title: Advanced configuration mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-logstash-advanced-configuration.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Advanced configuration [k8s-logstash-advanced-configuration] +# Advanced configuration for {{ls}} on {{eck}} [k8s-logstash-advanced-configuration] ## Setting JVM options [k8s-logstash-jvm-options] diff --git a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md index f3ca527a92..8f5662b7a7 100644 --- a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md +++ b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server.md @@ -1,4 +1,5 @@ --- +navigation_title: Advanced configuration mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-maps-advanced-configuration.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Advanced configuration [k8s-maps-advanced-configuration] +# Advanced configuration for Elastic Maps Server on {{eck}} [k8s-maps-advanced-configuration] ::::{warning} This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. diff --git a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md index 241a73fb2e..28afd9721e 100644 --- a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md @@ -1,4 +1,5 @@ --- +navigation_title: Advanced configuration mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-apm-advanced-configuration.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Advanced configuration [k8s-apm-advanced-configuration] +# Advanced configuration for {{apm-server}} on {{eck}} [k8s-apm-advanced-configuration] This section covers the following topics: diff --git a/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md b/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md index d358fe43f8..fcb9806052 100644 --- a/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md @@ -1,4 +1,5 @@ --- +navigation_title: Advanced configuration mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-kibana-advanced-configuration.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Advanced configuration [k8s-kibana-advanced-configuration] +# Advanced {{kib}} deployment and configuration on {{eck}} [k8s-kibana-advanced-configuration] If you already looked at the [{{es}} on ECK](elasticsearch-configuration.md) documentation, some of these concepts might sound familiar to you. The resource definitions in ECK share the same philosophy when you want to: diff --git a/deploy-manage/deploy/cloud-on-k8s/quickstart-beats.md b/deploy-manage/deploy/cloud-on-k8s/quickstart-beats.md index 9ac41a5dd7..2d9773d4cf 100644 --- a/deploy-manage/deploy/cloud-on-k8s/quickstart-beats.md +++ b/deploy-manage/deploy/cloud-on-k8s/quickstart-beats.md @@ -1,4 +1,5 @@ --- +navigation_title: Quickstart mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-beat-quickstart.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Quickstart [k8s-beat-quickstart] +# Quickstart: Running {{beats}} on {{eck}} [k8s-beat-quickstart] 1. Apply the following specification to deploy Filebeat and collect the logs of all containers running in the Kubernetes cluster. ECK automatically configures the secured connection to an {{es}} cluster named `quickstart`, created in [](/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md). diff --git a/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md b/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md index a3d8f912c3..4533e8e3d9 100644 --- a/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md +++ b/deploy-manage/deploy/cloud-on-k8s/quickstart-fleet.md @@ -1,4 +1,5 @@ --- +navigation_title: Quickstart mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-elastic-agent-fleet-quickstart.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Quickstart [k8s-elastic-agent-fleet-quickstart] +# Quickstart: Running {{fleet}} on {{eck}} [k8s-elastic-agent-fleet-quickstart] 1. To deploy {{fleet-server}}, {{agents}}, {{es}}, and {{kib}}, apply the following specification: diff --git a/deploy-manage/deploy/cloud-on-k8s/quickstart-logstash.md b/deploy-manage/deploy/cloud-on-k8s/quickstart-logstash.md index ef9e20c617..279d79d75f 100644 --- a/deploy-manage/deploy/cloud-on-k8s/quickstart-logstash.md +++ b/deploy-manage/deploy/cloud-on-k8s/quickstart-logstash.md @@ -1,4 +1,5 @@ --- +navigation_title: Quickstart mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-logstash-quickstart.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Quickstart [k8s-logstash-quickstart] +# Quickstart: Running {{ls}} on {{eck}} [k8s-logstash-quickstart] Add the following specification to create a minimal {{ls}} deployment that will listen to a Beats agent or Elastic Agent configured to send to Logstash on port 5044, create the service and write the output to an {{es}} cluster named `quickstart`, created in [](/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md). diff --git a/deploy-manage/deploy/cloud-on-k8s/quickstart-standalone.md b/deploy-manage/deploy/cloud-on-k8s/quickstart-standalone.md index d88086bc19..ebf9ae32d0 100644 --- a/deploy-manage/deploy/cloud-on-k8s/quickstart-standalone.md +++ b/deploy-manage/deploy/cloud-on-k8s/quickstart-standalone.md @@ -1,4 +1,5 @@ --- +navigation_title: Quickstart mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-elastic-agent-quickstart.html applies_to: @@ -8,7 +9,7 @@ products: - id: cloud-kubernetes --- -# Quickstart [k8s-elastic-agent-quickstart] +# Quickstart: Running standalone {{agent}} on {{eck}} [k8s-elastic-agent-quickstart] 1. Apply the following specification to deploy Elastic Agent with the System metrics integration to harvest CPU metrics from the Agent Pods. ECK automatically configures the secured connection to an {{es}} cluster named `quickstart`, created in [](/deploy-manage/deploy/cloud-on-k8s/elasticsearch-deployment-quickstart.md). diff --git a/deploy-manage/deploy/elastic-cloud/access-kibana.md b/deploy-manage/deploy/elastic-cloud/access-kibana.md index a0844b6265..74668a51eb 100644 --- a/deploy-manage/deploy/elastic-cloud/access-kibana.md +++ b/deploy-manage/deploy/elastic-cloud/access-kibana.md @@ -1,4 +1,5 @@ --- +navigation_title: Access {{kib}} mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-access-kibana.html - https://www.elastic.co/guide/en/cloud-heroku/current/ech-access-kibana.html @@ -10,7 +11,7 @@ products: - id: cloud-hosted --- -# Access {{kib}} [ec-access-kibana] +# Access {{kib}} on {{ech}} [ec-access-kibana] % What needs to be done: Lift-and-shift diff --git a/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md b/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md index ea19c6c561..66947e6bb3 100644 --- a/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md +++ b/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md @@ -1,4 +1,5 @@ --- +navigation_title: Add plugins and extensions mapped_pages: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-adding-plugins.html - https://www.elastic.co/guide/en/cloud-heroku/current/ech-adding-elastic-plugins.html @@ -10,7 +11,7 @@ products: - id: cloud-hosted --- -# Add plugins and extensions [ec-adding-plugins] +# Add plugins and extensions in {{ech}} [ec-adding-plugins] Plugins extend the core functionality of {{es}}. There are many suitable plugins, including: diff --git a/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md b/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md index af1b4ad638..bf9640be74 100644 --- a/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md +++ b/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md @@ -70,7 +70,7 @@ To make sure you’re all set for production, consider the following actions: * [Plan for your expected workloads](/deploy-manage/production-guidance.md) and consider how many availability zones you’ll need. * [Create a deployment](/deploy-manage/deploy/elastic-cloud/create-an-elastic-cloud-hosted-deployment.md) on the region you need and with a hardware profile that matches your use case. * [Change your configuration](/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md) by turning on autoscaling, adding high availability, or adjusting components of the {{stack}}. -* [Add extensions and plugins](/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md) to use Elastic supported extensions or add your own custom dictionaries and scripts. +* [Add plugins and extensions](/deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md) to use Elastic supported extensions or add your own custom dictionaries and scripts. * [Edit settings and defaults](/deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) to fine tune the performance of specific features. * [Manage your deployment](/deploy-manage/deploy/elastic-cloud/manage-deployments.md) as a whole to restart, upgrade, stop routing, or delete. * [Set up monitoring](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md) to learn how to configure your deployments for observability, which includes metric and log collection, troubleshooting views, and cluster alerts to automate performance monitoring. diff --git a/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md b/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md index 9072d550ba..83aac0ae7b 100644 --- a/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md +++ b/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md @@ -1,4 +1,5 @@ --- +navigation_title: Keep track of deployment activity mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-activity-page.html - https://www.elastic.co/guide/en/cloud-heroku/current/ech-activity-page.html @@ -9,7 +10,7 @@ products: - id: cloud-hosted --- -# Keep track of deployment activity +# Keep track of deployment activity on {{ech}} % What needs to be done: Lift-and-shift diff --git a/deploy-manage/deploy/self-managed/access-kibana.md b/deploy-manage/deploy/self-managed/access-kibana.md index 045e7e911e..580919a7b2 100644 --- a/deploy-manage/deploy/self-managed/access-kibana.md +++ b/deploy-manage/deploy/self-managed/access-kibana.md @@ -1,4 +1,5 @@ --- +navigation_title: Access {{kib}} mapped_pages: - https://www.elastic.co/guide/en/kibana/current/access.html applies_to: @@ -8,7 +9,7 @@ products: - id: kibana --- -# Access {{kib}} [access] +# Access {{kib}} in a self-managed cluster [access] Access {{kib}} through the web application on port 5601. diff --git a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md index cabeac2fb7..76388f27ae 100644 --- a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md +++ b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md @@ -9,10 +9,7 @@ products: - id: elasticsearch --- - - - -# Legacy collection methods [collecting-monitoring-data] +# Legacy collection methods for self-managed {{es}} [collecting-monitoring-data] ::::{admonition} Deprecated in 7.16 diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md index f70549cf06..6ca77e97fb 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md @@ -12,7 +12,7 @@ products: -# Legacy collection methods [monitoring-kibana] +# Legacy collection methods for self-managed {{kib}} [monitoring-kibana] If you enable the Elastic {{monitor-features}} in your cluster, you can optionally collect metrics about {{kib}}. diff --git a/deploy-manage/tools/cross-cluster-replication/_prerequisites_14.md b/deploy-manage/tools/cross-cluster-replication/_prerequisites_14.md index b22f046e84..af5337591e 100644 --- a/deploy-manage/tools/cross-cluster-replication/_prerequisites_14.md +++ b/deploy-manage/tools/cross-cluster-replication/_prerequisites_14.md @@ -1,4 +1,5 @@ --- +navigation_title: Prerequisites mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/_prerequisites_14.html applies_to: @@ -11,7 +12,7 @@ products: - id: elasticsearch --- -# Prerequisites [_prerequisites_14] +# Prerequisites for uni-directional disaster recovery [_prerequisites_14] Before completing this tutorial, [set up cross-cluster replication](set-up-cross-cluster-replication.md) to connect two clusters and configure a follower index. diff --git a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md index 5096f83d8c..55c9fc161e 100644 --- a/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md +++ b/deploy-manage/tools/cross-cluster-replication/ccr-getting-started-prerequisites.md @@ -1,4 +1,5 @@ --- +navigation_title: Prerequisites mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/ccr-getting-started-prerequisites.html applies_to: @@ -11,7 +12,7 @@ products: - id: elasticsearch --- -# Prerequisites [ccr-getting-started-prerequisites] +# Prerequisites for {{ccr}} [ccr-getting-started-prerequisites] To complete this tutorial, you need: diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md index fa407e8070..a4bc343705 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md @@ -1,4 +1,5 @@ --- +navigation_title: Quickstart mapped_pages: - https://www.elastic.co/guide/en/kibana/current/tutorial-secure-access-to-kibana.html applies_to: @@ -11,7 +12,7 @@ products: - id: kibana --- -# Quickstart [tutorial-secure-access-to-kibana] +# Quickstart: Native {{es}} user and role management [tutorial-secure-access-to-kibana] If you plan to use native {{es}} user and role management, then you can manage your users and roles completely within your {{kib}} instance. diff --git a/solutions/observability/apm/control-access-to-apm-data.md b/solutions/observability/apm/control-access-to-apm-data.md index bab9e5e177..fc7fba1115 100644 --- a/solutions/observability/apm/control-access-to-apm-data.md +++ b/solutions/observability/apm/control-access-to-apm-data.md @@ -330,7 +330,7 @@ POST /_security/role/staging_apm_viewer The last thing to do is assign users to the newly created roles above. Users will only have access to the data within the spaces that they are granted. -For information on how to create users and assign them roles with the {{kib}} UI, see [Securing access to Kibana](/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md). +For information on how to create users and assign them roles with the {{kib}} UI, see [](/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md). Alternatively, you can use the {{es}} [Create or update users API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-user).