Rewrite APM get started docs #2310
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdbirnstiehl
approved these changes
Jul 29, 2025
bmorelli25
reviewed
Jul 29, 2025
leemthompo
approved these changes
Jul 30, 2025
alexandra5000
approved these changes
Jul 30, 2025
This was referenced Aug 5, 2025
colleenmcginnis
added a commit
that referenced
this pull request
Aug 7, 2025
In #2310 we moved the Fleet-managed and APM Server binary getting started guides to the Fleet and Elastic Agent section of the reference documentation. Then Fleet-managed guide could possibly belong there, but the APM binary guide definitely doesn't since it doesn't use Fleet or Elastic Agent. Here's my proposal: * Create a new [Work with APM Server](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2410/solutions/observability/apm/apm-server) section (a working title) in the Observability solution section of the docs. * Put the existing APM Server specific content ([Configure APM Server](https://www.elastic.co/docs/solutions/observability/apm/configure-apm-server) and [Monitor APM Server](https://www.elastic.co/docs/solutions/observability/apm/monitor-apm-server)) into the new _Work with APM Server_ section. * Create a new subsection in [Work with APM Server](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2410/solutions/observability/apm/apm-server) that will contain the Fleet-managed and APM Server binary getting started guides. In this draft PR I called it [Set up](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2410/solutions/observability/apm/apm-server-setup) to avoid using _Get started_, but I'm not sure if that's the right title. * Recreates the comparison content that was removed in #2310 on the [Set up](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2410/solutions/observability/apm/apm-server-setup) page. * Delete the Fleet-managed and APM Server binary getting started guides from the Fleet and Elastic Agent section. Alternatives considered: * Keeping the Fleet-managed getting started guide in the Fleet and Elastic Agent section of the reference docs, and only moving the binary guide. * **Why not?** It makes more sense (especially to me) to keep these two guides close together alongside the content that helps users decide between the two approaches. * Moving both the old getting started guides into a new APM Server section of the reference section. * **Why not?** The bulk of the APM Server content is well-established in the solutions guide. I think users will have a hard time finding previously established solutions content in a new reference section that contains only non-reference content. Is there an alternative approach I'm not considering? cc @bmorelli25 @theletterf @simitt --------- Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2309