Skip to content

Fix APM ES config documentation to correctly indicate applicability to both binary and Fleet-managed deployments #3343

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix APM ES config documentation to correctly indicate applicability to both binary and Fleet-managed deployments #3343

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
636a8ce
Initial plan
Copilot Oct 6, 2025
0a82481
Fix APM ES config documentation to show it applies to both binary and…
Copilot Oct 6, 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 solutions/observability/apm/apm-server/configure-elasticsearch-output.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ products:
# Configure the Elasticsearch output for APM Server[apm-elasticsearch-output]

::::{note}
![supported deployment methods](/solutions/images/observability-binary-yes-fm-no.svg "")
![supported deployment methods](/solutions/images/observability-binary-yes-fm-yes.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 here apply to both APM Server binary and Fleet-managed users. The YAML configuration examples shown are specific to APM Server binary users. Fleet-managed users should configure these same APM-specific {{es}} output settings through the {{fleet}} UI rather than the general [{{es}} output settings](/reference/fleet/elasticsearch-output.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit hesitant about the part rather than the general ... which is a "negative" link to /reference/fleet/elasticsearch-output.md because it wants to call out that Fleet ES config does not apply to ES output if used in APM. This may create confusion, but at the same time clears out some confusion. I think it is fine, unless we have a better way to express that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fleet-managed users should configure these same APM-specific {{es}} output settings through the {{fleet}} UI

When you say it should be configured in the Fleet UI, do you mean it as described here or something else?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly. Editing the Elasticsearch Output, but put in configs documented in the APM docs inside the Elasticsearch output Advanced YAML config text box.


::::

Expand Down
Loading