Skip to content

Update remote-elasticsearch-output.md #1602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 4, 2025
Merged

Update remote-elasticsearch-output.md #1602

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d1e31fc
Update remote-elasticsearch-output.md
tailorzed Jun 4, 2025
2aca6e7
Update remote-elasticsearch-output.md
theletterf Jun 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions reference/fleet/remote-elasticsearch-output.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,15 @@ Remote {{es}} outputs allow you to send {{agent}} data to a remote {{es}} cluste
A remote {{es}} cluster supports the same [output settings](/reference/fleet/es-output-settings.md) as your main {{es}} cluster.

::::{note}
Note the following restrictions with the remote {es} output:
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.
::::

## Limitations

These limitations apply to remote {es} output:

* Using a remote {{es}} output with a target cluster that has [traffic filters](/deploy-manage/security/traffic-filtering.md) enabled is not currently supported.
* Using {{elastic-defend}} is currently not supported when a remote {{es}} output is configured for an agent.
::::

## Configuration

Expand Down
Loading