From 3965b18558e1a4f9c94012a9a0c6afa94a521ff3 Mon Sep 17 00:00:00 2001 From: Karen Metts <35154725+karenzone@users.noreply.github.com> Date: Tue, 18 Feb 2025 19:05:12 -0500 Subject: [PATCH 1/3] Update upgrading-stack-on-prem.asciidoc Logstash with the elastic_integration filter requires a different installation order --- .../upgrading-stack-on-prem.asciidoc | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc index e2bc23631..846e2d653 100644 --- a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc @@ -1,21 +1,28 @@ [[upgrading-elastic-stack-on-prem]] == Upgrade Elastic on self-managed infrastructure -Once you are <>, +When you are <>, you will need to upgrade each of your Elastic components individually. . Consider closing {ml} jobs before you start the upgrade process. While {ml} jobs can continue to run during a rolling upgrade, it increases the overhead on the cluster during the upgrade process. -. Upgrade the components of your {stack} in the following order: +. Upgrade the components of your {stack} in this order: + //.. {es} Hadoop: {hadoop-ref}/install.html[install instructions] .. {es}: <> .. {kib}: <> //.. Java API Client: {java-api-client}/installation.html#maven[dependency configuration] -.. {ls}: {logstash-ref}/upgrading-logstash.html[upgrade instructions] +.. {ls}: {logstash-ref}/upgrading-logstash.html[upgrade instructions] (See note below) .. {beats}: {beats-ref}/upgrading.html[upgrade instructions] .. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] -.. {apm-agent}s {observability-guide}/apm-upgrade.html[upgrade instructions] \ No newline at end of file +.. {apm-agent}s {observability-guide}/apm-upgrade.html[upgrade instructions] + +.Additional guidance for `logstash-filter-elastic` plugin users +=== +If you are using {ls} to extend Elastic integrations with the `logstash-filter-elastic_integration` plugin, upgrade {ls} (or the `logstash-filter-elastic_integration` plugin specifically) _before_ you upgrade {kib}. + +The {es}-{ls}-{kib} installation order for this specific plugin and use case ensures the best experience with {agent}-managed pipelines, and embeds functionality from a version of {es} Ingest Node that is compatible with the plugin version (`major`.`minor`). +=== From b824708bc85a5e7f8f77d17d9b898701ec7f8ed6 Mon Sep 17 00:00:00 2001 From: Karen Metts <35154725+karenzone@users.noreply.github.com> Date: Tue, 18 Feb 2025 19:44:43 -0500 Subject: [PATCH 2/3] Reformat as a note --- .../install-upgrade/upgrading-stack-on-prem.asciidoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc index 846e2d653..58074c0c7 100644 --- a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc @@ -20,9 +20,9 @@ on the cluster during the upgrade process. .. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] .. {apm-agent}s {observability-guide}/apm-upgrade.html[upgrade instructions] -.Additional guidance for `logstash-filter-elastic` plugin users -=== -If you are using {ls} to extend Elastic integrations with the `logstash-filter-elastic_integration` plugin, upgrade {ls} (or the `logstash-filter-elastic_integration` plugin specifically) _before_ you upgrade {kib}. +[NOTE] +-- +If you are using {ls} to extend Elastic integrations with the {logstash-ref}/plugins-filters-elastic_integration.html[`logstash-filter-elastic_integration`] plugin, upgrade {ls} (or the `logstash-filter-elastic_integration` plugin specifically) _before_ you upgrade {kib}. -The {es}-{ls}-{kib} installation order for this specific plugin and use case ensures the best experience with {agent}-managed pipelines, and embeds functionality from a version of {es} Ingest Node that is compatible with the plugin version (`major`.`minor`). -=== +The {es}-{ls}-{kib} installation order for this specific plugin ensures the best experience with {agent}-managed pipelines, and embeds functionality from a version of {es} Ingest Node that is compatible with the plugin version (`major`.`minor`). +-- From ae1e139609edf8eb64782a93acae9652cb019da7 Mon Sep 17 00:00:00 2001 From: Karen Metts <35154725+karenzone@users.noreply.github.com> Date: Wed, 19 Feb 2025 10:50:48 -0500 Subject: [PATCH 3/3] Refine content --- docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc index 58074c0c7..883a1144c 100644 --- a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc @@ -22,7 +22,7 @@ on the cluster during the upgrade process. [NOTE] -- -If you are using {ls} to extend Elastic integrations with the {logstash-ref}/plugins-filters-elastic_integration.html[`logstash-filter-elastic_integration`] plugin, upgrade {ls} (or the `logstash-filter-elastic_integration` plugin specifically) _before_ you upgrade {kib}. +If you are using {ls} and the {logstash-ref}/plugins-filters-elastic_integration.html[`logstash-filter-elastic_integration`] plugin to extend Elastic integrations, upgrade {ls} (or the `logstash-filter-elastic_integration` plugin specifically) _before_ you upgrade {kib}. The {es}-{ls}-{kib} installation order for this specific plugin ensures the best experience with {agent}-managed pipelines, and embeds functionality from a version of {es} Ingest Node that is compatible with the plugin version (`major`.`minor`). --