You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the Remote Elasticsearch output is an Enterprise feature, I wish
to display this information there.
---------
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
Copy file name to clipboardExpand all lines: reference/fleet/remote-elasticsearch-output.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,15 @@ Remote {{es}} outputs allow you to send {{agent}} data to a remote {{es}} cluste
13
13
A remote {{es}} cluster supports the same [output settings](/reference/fleet/es-output-settings.md) as your main {{es}} cluster.
14
14
15
15
::::{note}
16
-
Note the following restrictions with the remote {es} output:
16
+
This feature is part of the Enterprise subscription offering under the name of **Per Integration output assignment**. Refer to [Subscriptions](https://www.elastic.co/subscriptions) for more information.
17
+
::::
18
+
19
+
## Limitations
20
+
21
+
These limitations apply to remote {es} output:
17
22
18
23
* Using a remote {{es}} output with a target cluster that has [traffic filters](/deploy-manage/security/traffic-filtering.md) enabled is not currently supported.
19
24
* Using {{elastic-defend}} is currently not supported when a remote {{es}} output is configured for an agent.
0 commit comments