Skip to content

Fix the applies_to tag position in manage-elastic-agents-in-fleet.md #3432

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 3 commits into from
Oct 9, 2025
+2 −2
Merged

Fix the applies_to tag position in manage-elastic-agents-in-fleet.md #3432

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0bc7cc5
Fix the applies_to tag position in manage-elastic-agents-in-fleet.md
vishaangelova Oct 9, 2025
757e7f8
Merge branch 'main' into vishaangelova-patch-1
vishaangelova Oct 9, 2025
564c32c
Merge branch 'main' into vishaangelova-patch-1
vishaangelova Oct 9, 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
4 changes: 2 additions & 2 deletions reference/fleet/manage-elastic-agents-in-fleet.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,8 @@ Find **{{fleet}}** in the {{kib}} navigation menu, or use the [global search fie
In {{fleet}} deployments where {{agents}} are installed in diverse locations and where data must be stored in local clusters, operators need a unified view of all agents and a central management interface for tasks like upgrades, policy organization, and metrics collection. {{fleet}} offers features to facilitate this deployment model:

- [Remote {{es}} output](/reference/fleet/remote-elasticsearch-output.md): Configure {{agents}} to send data to remote {{es}} clusters while still sending their check-in payloads to the management cluster. This allows {{fleet}} on the management cluster to maintain a global view of all agents while the ingested data is routed to the agents' respective local clusters.
- [Automatic integrations synchronization](/reference/fleet/automatic-integrations-synchronization.md) {applies_to}`stack: ga 9.1.0`: Install an integration once in the management cluster and use {{fleet}} to synchronize and update the integration across all remote clusters. This enables you to initiate services like [OSquery](integration-docs://reference/osquery-intro.md) from the management cluster, and to collect and display responses from dispersed agents in {{fleet}} on the central management cluster.
- {applies_to}`stack: ga 9.1.0` [Automatic integrations synchronization](/reference/fleet/automatic-integrations-synchronization.md): Install an integration once in the management cluster and use {{fleet}} to synchronize and update the integration across all remote clusters. This enables you to initiate services like [OSquery](integration-docs://reference/osquery-intro.md) from the management cluster, and to collect and display responses from dispersed agents in {{fleet}} on the central management cluster.

:::{image} images/manage-agents-global-fleet.png
:alt: A diagram showing Elastic Agents connected to remote data clusters and to a Fleet management cluster
:::
:::
Loading