From 6a082177da11d79d785cbc3717fd2ddadc54cc51 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 6 Oct 2025 14:27:15 +0000
Subject: [PATCH 1/2] Initial plan


From e1845e7607f1138d203a0f24faebf8d4feaf8022 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 6 Oct 2025 14:31:10 +0000
Subject: [PATCH 2/2] Fix APM ES output docs to clarify applicability to
 Fleet-managed users

Co-authored-by: carsonip <9133397+carsonip@users.noreply.github.com>
---
 .../apm/apm-server/configure-elasticsearch-output.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/solutions/observability/apm/apm-server/configure-elasticsearch-output.md b/solutions/observability/apm/apm-server/configure-elasticsearch-output.md
index 9db3a9b4ce..0e77535afd 100644
--- a/solutions/observability/apm/apm-server/configure-elasticsearch-output.md
+++ b/solutions/observability/apm/apm-server/configure-elasticsearch-output.md
@@ -14,7 +14,7 @@ products:
 ::::{note}
 ![supported deployment methods](/solutions/images/observability-binary-yes-fm-no.svg "")
 
-This documentation only applies to APM Server binary users. Fleet-managed users should see [Configure the {{es}} output](/reference/fleet/elasticsearch-output.md).
+The configuration options described in this documentation apply to both APM Server binary and Fleet-managed APM Server. However, the YAML configuration method shown here only applies to APM Server binary users. Fleet-managed users configure these same APM-specific Elasticsearch output settings through the Fleet UI in Kibana.
 
 ::::