Merge branch 'main' into 6394-detections-alerts-sections-reorg

Author: benironside

deploy-manage/deploy/elastic-cloud/edit-stack-settings.md

@@ -59,7 +59,7 @@ Change how {{es}} runs by providing your own user settings. {{ech}} appends thes
 
 {{ech}} automatically rejects `elasticsearch.yml` settings that could break your cluster.
 
-For a list of supported settings, check [Supported {{es}} settings](elasticsearch://reference/elasticsearch/configuration-reference/elastic-cloud-hosted-elasticsearch-settings.md).
+For a list of supported settings, check [Supported {{es}} settings](elasticsearch://reference/elasticsearch/configuration-reference/index.md).
 
 ::::{warning}
 You can also update [dynamic cluster settings](../../../deploy-manage/deploy/self-managed/configure-elasticsearch.md#dynamic-cluster-setting) using {{es}}'s [update cluster settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings). However, {{ech}} doesn’t reject unsafe setting changes made using this API. Use it with caution.

deploy-manage/deploy/self-managed/_snippets/third-party-dependencies.md

@@ -0,0 +1 @@
+Refer to [{{stack}} third-party dependencies](https://artifacts.elastic.co/reports/dependencies/dependencies-current.html) for the complete list of dependencies.

deploy-manage/deploy/self-managed/install-kibana.md

@@ -52,4 +52,9 @@ Running different patch version releases of {{kib}} and {{es}} (e.g. {{kib}} 9.0
 ## Installation order
 
 :::{include} /deploy-manage/deploy/_snippets/installation-order.md
-:::
+:::
+
+## Third-party dependencies
+
+:::{include} /deploy-manage/deploy/self-managed/_snippets/third-party-dependencies.md
+:::

deploy-manage/deploy/self-managed/installing-elasticsearch.md

@@ -104,4 +104,5 @@ Don’t use third-party Java agents that attach to the JVM. These agents can red
 
 ## Third-party dependencies [dependencies-versions]
 
-See [Elastic Stack third-party dependencies](https://artifacts.elastic.co/reports/dependencies/dependencies-current.html) for the complete list of dependencies for {{es}}.
+:::{include} /deploy-manage/deploy/self-managed/_snippets/third-party-dependencies.md
+:::

deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md

@@ -82,7 +82,7 @@ The PagerDuty integration consists of the following parts:
 
 **AutoOps configuration**
 
-1. Add a new PagerDuty endpoint using the PagerDuty configuration application key.
+1. Add a new PagerDuty connector using the PagerDuty configuration application key.
 2. To receive Slack notifications, add a notification filter. Scroll down the Notification page and click **Add**.
 3. Fill in the filter details.
 4. Select the events that should be sent to this output.
@@ -100,8 +100,8 @@ To set up a webhook to send AutoOps notifications to a Slack channel, go through
 6. Toggle the **Activate Incoming Webhooks** to On.
 7. Click **Request to Add New Webhook**.
 8. Select a Slack channel from the list to receive the notifications and click **Allow**.
-9. Copy the webhook URL to set up the webhook notification endpoint in AutoOps.
-10. Add the webhook URL when creating the endpoint.
+9. Copy the webhook URL to set up the webhook notification connector in AutoOps.
+10. Add the webhook URL when creating the connector.
 
 
 ### VictorOps [ec-autoops-victorops]
@@ -115,7 +115,7 @@ The VictorOps integration consists of the following parts:
 
 **AutoOps configuration**
 
-1. Add a new PagerDuty endpoint using the PagerDuty configuration application key.
+1. Add a new PagerDuty connector using the PagerDuty configuration application key.
 2. To receive Slack notifications, add a notification filter. Scroll down the Notification page and click Add.
 3. Fill in the filter details.
 4. Select the events that should be sent to this output.
@@ -137,7 +137,7 @@ The Opsgenie integration consists of the following parts:
 
 1. Open AutoOps and go to **User Profile**. Then, select **Notifications**.
 2. Click **Add** and select **Opsgenie** from the dropdown list.
-3. Name your endpoint and add Api Key from opsgenie API configuration. Click the validate button to make sure that your notification setting is working. Don’t forget to save your notification endpoint!
+3. Name your connector and add Api Key from opsgenie API configuration. Click the validate button to make sure that your notification setting is working. Don’t forget to save your notification connector!
 4. To receive notifications on Opsgenie, you need to add a notification filter. Scroll down the **Notification** page and click **Add**.
 5. Fill in the filter details.
 6. Select events that should be sent to this output.
@@ -151,7 +151,7 @@ Save the URL displayed during the creation of the incoming webhook, as you will
 
 **AutoOps configuration**
 
-1. Add a new MS team endpoint using the URL from Microsoft Teams.
+1. Add a new MS team connector using the URL from Microsoft Teams.
 2. To receive notifications into Microsoft Teams, you need to add a notification filter. Scroll down the Notification page and click Add.
 3. Fill in the filter details.
 4. Select events that should be sent to this output.
@@ -163,7 +163,7 @@ A webhook enables an application to provide other applications with real-time in
 
 **How to add a webhook notification**
 
-1. Go to **Settings** → **Notifications*** → ***Endpoint settings** and click **Add**.
+1. Go to **Settings** → **Notifications*** → ***Connector settings** and click **Add**.
 2. Select Webhook from the drop-dowon list and enter the following details:
 
     * Name: It must be a unique name for this webhook.
@@ -191,7 +191,7 @@ A webhook enables an application to provide other applications with real-time in
 5. Optionally, you can test the webhook integration by using the [webhook.site](https://webhook.site/#!/view/fe9d630e-2f01-44b7-9e41-ef9520fbe9a7).
 
 ::::{note}
-When the Endpoint settings have been completed, continue to set up the notification filter to define which events you’d like to be notified about.
+When the connector settings have been completed, continue to set up the notification filter to define which events you’d like to be notified about.
 ::::
 
 ## Notifications report [ec-notification-report]

deploy-manage/upgrade/orchestrator/upgrade-cloud-enterprise.md

@@ -51,7 +51,7 @@ Before starting the upgrade process, check which of the following recommendation
 
 
 * We strongly recommend that you routinely update your ECE installation to the most current version so that any bugs and security issues are fixed promptly. If you need to upgrade but are currently experiencing any issues with your platform, note that as long as ZooKeeper is running and healthy you should be able to upgrade (you can use the [get runners API](https://www.elastic.co/docs/api/doc/cloud-enterprise/operation/operation-get-runners) to easily verify the health of the runners on the [ECE allocators](../../../deploy-manage/deploy/cloud-enterprise/ece-architecture.md#ece-architecture-allocators)). That is, healthy system deployments are not required in order to perform an upgrade successfully.
-* Before upgrading to Elastic Cloud Enterprise 4.0, refer to the [lists of removals](/release-notes/breaking-changes/index.md) to find out about features and API endpoints that are no longer supported.
+* Before upgrading to Elastic Cloud Enterprise 4.0, refer to the [lists of removals](cloud://release-notes/cloud-enterprise/breaking-changes.md) to find out about features and API endpoints that are no longer supported.
 * We strongly recommend that you do not attempt to perform certain actions during the upgrade process, such as:
 
     * Creating or changing Elasticsearch clusters and Kibana instances

docset.yml

@@ -384,10 +384,16 @@ subs:
   multi-arg-ref:   "†footnoteref:[multi-arg]"
   yes-icon:   "image:https://doc-icons.s3.us-east-2.amazonaws.com/icon-yes.png[Yes,20,15]"
   no-icon:   "image:https://doc-icons.s3.us-east-2.amazonaws.com/icon-no.png[No,20,15]"
+  agent-repo:   "https://github.com/elastic/elastic-agent/"
+  agent-issue:   "https://github.com/elastic/elastic-agent/issues/"
+  agent-pull:   "https://github.com/elastic/elastic-agent/pull/"
   es-repo:   "https://github.com/elastic/elasticsearch/"
   es-issue:   "https://github.com/elastic/elasticsearch/issues/"
   es-pull:   "https://github.com/elastic/elasticsearch/pull/"
   es-commit:   "https://github.com/elastic/elasticsearch/commit/"
+  fleet-server-repo:   "https://github.com/elastic/fleet-server/"
+  fleet-server-issue:   "https://github.com/elastic/fleet-server/issues/"
+  fleet-server-pull:   "https://github.com/elastic/fleet-server/pull/"
   kib-repo:   "https://github.com/elastic/kibana/"
   kib-issue:   "https://github.com/elastic/kibana/issues/"
   kibana-issue:   "'{kib-repo}issues/'"

explore-analyze/machine-learning/nlp/ml-nlp-elser.md

@@ -57,7 +57,7 @@ The easiest and recommended way to download and deploy ELSER is to use the [{{in
 2. Create an {{infer}} endpoint with the ELSER service by running the following API request:
 
 ```console
-PUT _inference/sparse_embedding/my-elser-model
+PUT _inference/sparse_embedding/my-elser-endpoint
     {
       "service": "elasticsearch",
       "service_settings": {
@@ -67,7 +67,7 @@ PUT _inference/sparse_embedding/my-elser-model
           "max_number_of_allocations": 10
         },
         "num_threads": 1,
-        "model_id": ".elser_model_2_linux-x86_64"
+        "model_id": ".elser_model_2"
       }
     }
 ```

raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md

@@ -20,7 +20,7 @@ Upgrading from a release candidate build, such as 8.0.0-rc1 or 8.0.0-rc2, is not
     * [{{es}} migration guide](elasticsearch://release-notes/breaking-changes.md)
     * [{{elastic-sec}} release notes](https://www.elastic.co/guide/en/security/current/release-notes.html)
     * [{{ents}} release notes](https://www.elastic.co/guide/en/enterprise-search/current/changelog.html)
-    * [{{fleet}} and {{agent}} release notes](/release-notes/fleet-elastic-agent.md)
+    * [{{fleet}} and {{agent}} release notes](/release-notes/fleet-elastic-agent/release-notes.md)
     * [{{kib}} release notes](kibana://release-notes/index.md)
     * [{{ls}} breaking changes](logstash://release-notes/breaking-changes.md)
 

reference/data-analysis/observability/index.md

@@ -8,10 +8,10 @@ mapped_pages:
 
 Learn about the key metrics displayed in the Infrastructure app and how they are calculated.
 
-* [Host metrics](/reference/data-analysis/observability/observability-host-metrics-serverless.md)
-* [Container metrics](/reference/data-analysis/observability/observability-container-metrics-serverless.md)
-* [Kubernetes pod metrics](/reference/data-analysis/observability/observability-kubernetes-pod-metrics-serverless.md)
-* [AWS metrics](/reference/data-analysis/observability/observability-aws-metrics-serverless.md)
+* [Host metrics](/reference/data-analysis/observability/observability-host-metrics.md)
+* [Container metrics](/reference/data-analysis/observability/observability-container-metrics.md)
+* [Kubernetes pod metrics](/reference/data-analysis/observability/observability-kubernetes-pod-metrics.md)
+* [AWS metrics](/reference/data-analysis/observability/observability-aws-metrics.md)