From dc8d596972cb544dfebc258978089541a1760c88 Mon Sep 17 00:00:00 2001 From: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> Date: Mon, 29 Jul 2024 09:57:32 -0400 Subject: [PATCH] Add restriction about traffic filters with remote ES output (#1207) (cherry picked from commit c937133bcf1f1e3558b65d4400bb1f8618b4d194) --- .../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 b85e391b4..f548032f7 100644 --- a/docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc +++ b/docs/en/ingest-management/fleet/fleet-settings-remote-elasticsearch.asciidoc @@ -7,6 +7,8 @@ Beginning in version 8.12.0, you can send {agent} data to a remote {es} cluster. A remote {es} cluster supports the same <> as your main {es} cluster. +NOTE: Using a remote {es} output with a target cluster that has {cloud}/ec-traffic-filtering-deployment-configuration.html[traffic filters] enabled is not currently supported. + To configure a remote {es} cluster for your {agent} data: . In {fleet}, open the **Settings** tab.