Skip to content

Commit c1bd295

Browse files
Fix migrate integrations docs (#923) (#925)
(cherry picked from commit fc6bc07) Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
1 parent 576dd32 commit c1bd295

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

docs/en/ingest-management/fleet/migrate-elastic-agent.asciidoc

+12-2
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,7 @@ On your target cluster, certain settings from the original {ecloud} {agent} poli
123123

124124
To reset the {ecloud} {agent} policy:
125125

126-
. Open {kib} and navigate to *Management -> Dev Tools*.
127-
. Choose one of the API requests below and submit it through the console.
126+
. Choose one of the API requests below and submit it through a terminal window.
128127
** If you're using {kib} version 8.11 or higher, run:
129128
+
130129
[source,shell]
@@ -149,6 +148,17 @@ curl --request POST \
149148
+
150149
After running the command, your {ecloud} agent policy settings should all be updated appropriately.
151150

151+
[NOTE]
152+
====
153+
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}:
154+
155+
. From the {kib} menu, select *Manage this deployment*.
156+
. In the deployment menu, select *Integrations Server*.
157+
. On the *Integrations Server* page, select *Force Restart*.
158+
159+
After the restart, {integrations-server} will enroll a new {agent} for the {ecloud} agent policy and {fleet-server} should return to a healthy state.
160+
====
161+
152162
[discrete]
153163
[[migrate-elastic-agent-confirm-policy]]
154164
=== Confirm your policy settings

0 commit comments

Comments
 (0)