From 0a18ca079006e85a7b0a4318fc3950632b986325 Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Wed, 30 Apr 2025 10:49:03 -0400 Subject: [PATCH] [Backport] Add note about remote ES error with Fleet Server (#1786) (cherry picked from commit 9768e164e948a7df9acb9c29eb8a5cf5815da7a9) --- .../fleet/fleet-settings-remote-elasticsearch.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc b/docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc index 099f77f19..648d00cb8 100644 --- a/docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc +++ b/docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc @@ -68,3 +68,5 @@ After the output is created, you can update an {agent} policy to use the new rem The remote {es} cluster is now configured. As a final step before using the remote {es} output, you need to make sure that for any integrations that have been <>, the integration assets have been installed on the remote {es} cluster. Refer to <> for the steps. + +NOTE: When you use a remote {es} output, {fleet-server} performs a test to ensure connectivity to the remote cluster. The result of that connectivity test is used to report the ES Remote output as healthy or unhealthy on the **Fleet** > **Settings** > **Outputs** page, under the **Status** column. In some cases, the remote {es} output used for data from {agent} may be reachable only by those agents and not by {fleet-server}, so the unhealthy state and an associated `Unable to connect` error that appears on the UI can be ignored. \ No newline at end of file