Merge branch 'monitoring-pt2' of github.com:elastic/docs-content into monitoring-pt2

Author: shainaraskas

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/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/'"

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/ingestion-tools/fleet/upgrade-elastic-agent.md

@@ -226,13 +226,13 @@ For installation steps refer to [Install {{fleet}}-managed {{agent}}s](/referenc
 1. Download the {{agent}} Debian install package for the release that you want to upgrade to:
 
     ```bash
-    curl -L -O https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-9.0.0-beta1-amd64.deb
+    curl -L -O https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-{{stack-version}}-amd64.deb
     ```
 
 2. Upgrade {{agent}} to the target release:
 
     ```bash
-    sudo dpkg -i elastic-agent-9.0.0-beta1-amd64.deb
+    sudo dpkg -i elastic-agent-{{stack-version}}-amd64.deb
     ```
 
 3. Confirm in {{fleet}} that the agent has been upgraded to the target version. Note that the **Upgrade agent** option in the **Actions** menu next to the agent will be disabled since [fleet]-managed upgrades are not supported for this package type.
@@ -243,13 +243,13 @@ For installation steps refer to [Install {{fleet}}-managed {{agent}}s](/referenc
 1. Download the {{agent}} RPM install package for the release that you want to upgrade to:
 
     ```bash
-    curl -L -O https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-9.0.0-beta1-x86_64.rpm
+    curl -L -O https://artifacts.elastic.co/downloads/beats/elastic-agent/elastic-agent-{{stack-version}}-x86_64.rpm
     ```
 
 2. Upgrade {{agent}} to the target release:
 
     ```bash
-    sudo rpm -U elastic-agent-9.0.0-beta1-x86_64.rpm
+    sudo rpm -U elastic-agent-{{stack-version}}-x86_64.rpm
     ```
 
-3. Confirm in {{fleet}} that the agent has been upgraded to the target version. Note that the **Upgrade agent** option in the **Actions** menu next to the agent will be disabled since [fleet]-managed upgrades are not supported for this package type.
+3. Confirm in {{fleet}} that the agent has been upgraded to the target version. Note that the **Upgrade agent** option in the **Actions** menu next to the agent will be disabled since {{fleet}}-managed upgrades are not supported for this package type.