From e241c3db5c4c8a9790810a8c1a6cdc28c62f7adb Mon Sep 17 00:00:00 2001
From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Date: Thu, 15 Feb 2024 15:07:52 -0500
Subject: [PATCH] Fix migrate integrations docs (#923)
(cherry picked from commit fc6bc07ffba8cab3ee863045851365ce2b383f76)
---
.../fleet/migrate-elastic-agent.asciidoc | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/docs/en/ingest-management/fleet/migrate-elastic-agent.asciidoc b/docs/en/ingest-management/fleet/migrate-elastic-agent.asciidoc
index 1158a1f24..5cf17463f 100644
--- a/docs/en/ingest-management/fleet/migrate-elastic-agent.asciidoc
+++ b/docs/en/ingest-management/fleet/migrate-elastic-agent.asciidoc
@@ -123,8 +123,7 @@ On your target cluster, certain settings from the original {ecloud} {agent} poli
To reset the {ecloud} {agent} policy:
-. Open {kib} and navigate to *Management -> Dev Tools*.
-. Choose one of the API requests below and submit it through the console.
+. Choose one of the API requests below and submit it through a terminal window.
** If you're using {kib} version 8.11 or higher, run:
+
[source,shell]
@@ -149,6 +148,17 @@ curl --request POST \
+
After running the command, your {ecloud} agent policy settings should all be updated appropriately.
+[NOTE]
+====
+After running the command, a warning message may appear in {fleet} indicating that {fleet-server} is not healthy. As well, the {agent} associated with the {ecloud} agent policy may disappear from the list of agents. To remedy this, you can restart {integrations-server}:
+
+. From the {kib} menu, select *Manage this deployment*.
+. In the deployment menu, select *Integrations Server*.
+. On the *Integrations Server* page, select *Force Restart*.
+
+After the restart, {integrations-server} will enroll a new {agent} for the {ecloud} agent policy and {fleet-server} should return to a healthy state.
+====
+
[discrete]
[[migrate-elastic-agent-confirm-policy]]
=== Confirm your policy settings