Relocate APM Server getting started content

[colleenmcginnis]

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 section (a working title) in the Observability solution section of the docs.
• Put the existing APM Server specific content (Configure APM Server and Monitor APM Server) into the new Work with APM Server section.
• Create a new subsection in Work with APM Server that will contain the Fleet-managed and APM Server binary getting started guides. In this draft PR I called it Set up to avoid using Get started, but I'm not sure if that's the right title.
• Recreates the comparison content that was removed in Rewrite APM get started docs #2310 on the Set up 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

[github-actions]

⚠️ Markdown file changes detected

The following 2 Markdown files were renamed in this PR:

• reference/fleet/get-started-apm-server-binary.md → solutions/observability/apm/apm-server-binary.md
• reference/fleet/get-started-managed-apm-server.md → solutions/observability/apm/apm-server-fleet-managed.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

• Keep files whenever possible and hide them from the TOC by using hidden
• Add a notice at the top of the file indicating that the page has moved with a link to the new location
• Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

[theletterf]

@colleenmcginnis I love this. While working on #2310 I noticed APM Server docs needed a recognizable home. This PR provides just that. Good job!

I only left a couple comments to preserve Get Started links as they are in the intros.

[github-actions]

⚠️ Markdown file changes detected

The following 2 Markdown files were renamed in this PR:

• reference/fleet/get-started-apm-server-binary.md → solutions/observability/apm/apm-server-binary.md
• reference/fleet/get-started-managed-apm-server.md → solutions/observability/apm/apm-server-fleet-managed.md

Action Required

We currently do not have an easy way to implement redirects for removed or renamed files. If possible, please:

• Keep files whenever possible and hide them from the TOC by using hidden
• Add a notice at the top of the file indicating that the page has moved with a link to the new location
• Ensure you've updated redirects.yml accordingly if files must be removed or renamed

Thank you!

[github-actions]

🔍 Preview links for changed docs

• solutions/observability/apm/apm-server-setup.md
• solutions/observability/apm/apm-server.md
• reference/apm/observability/apm.md
• solutions/observability/apm/apm-server-advanced-setup.md
• solutions/observability/apm/configure-apm-server.md
• solutions/observability/apm/index.md
• solutions/observability/apm/monitor-apm-server.md
• solutions/observability/apm/switch-self-installation-to-apm-integration.md
• solutions/observability/apm/upgrade-self-installation-of-apm-server-standalone-to-9.md
• solutions/observability/apm/use-opentelemetry-with-apm.md

More links …

• solutions/observability/apm/apm-server-binary.md
• solutions/observability/apm/apm-server-fleet-managed.md

[florent-leborgne]

LGTM. I'll let @mdbirnstiehl take a quick look too since this is a significant move

[bmorelli25]

Keeping the Fleet-managed getting started guide in the Fleet and Elastic Agent section of the reference docs, and only moving the binary guide.

Agreed that keeping these two options side-by-side is best for our users.

Moving both the old getting started guides into a new APM Server section of the reference section.

a new reference section that contains only non-reference content

🤪 let's not do that.

I think this is the right approach. No notes on overall structure. Just a few comments on content.

[mdbirnstiehl]

Approach and content LGTM! 🐦

[simitt]

Left two notes, but generally looks good to keep apm-server docs together but less prominent.

[simitt]

Is ## Step 4: Install APM agents [apm-next-steps] still something that we want to show in this level of detail for the apm-server choice? Asking as there is also https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2410/solutions/observability/apm/elastic-apm-agents

[colleenmcginnis]

I'm going to leave that section as is for now so we can at least get these guides back into the observability docs. Let's discuss this in a follow-up issue.