Skip to content

Commit 010d22d

Browse files
Fix the applies_to tag position in manage-elastic-agents-in-fleet.md (#3432)
This PR fixes the position of the in-line `applies_to` tag to improve readability.
1 parent 7c1ef8d commit 010d22d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

reference/fleet/manage-elastic-agents-in-fleet.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ Find **{{fleet}}** in the {{kib}} navigation menu, or use the [global search fie
3838
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:
3939

4040
- [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.
41-
- [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.
41+
- {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.
4242

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

0 commit comments

Comments
 (0)