Remove standalone AAP's doc mentions to APM

[Julio-Guerra]

What does this PR do? What is the motivation?

Fix the standalone AAP setup landing page, removing incoherent details regarding APM.

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

/merge

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/julio.guerra/fix-aap-standalone-index/security/application_security/threats/setup/standalone/

[Julio-Guerra]

/merge

[dd-devflow]

View all feedbacks in Devflow UI.

2025-04-10 07:57:56 UTC ℹ️ Start processing command /merge

---

2025-04-10 07:58:02 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-04-10 11:58:06 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

[drichards-87]

@Julio-Guerra Can we hold off on merging this until Monday? We're getting the security nav PRs ready and are trying to avoid introducing any merge conflicts. I can also try and port these changes over manually into the main update PR that we're working on (which will be merged Monday morning).

[Julio-Guerra]

@Julio-Guerra Can we hold off on merging this until Monday? We're getting the security nav PRs ready and are trying to avoid introducing any merge conflicts. I can also try and port these changes over manually into the main update PR that we're working on (which will be merged Monday morning).

This new standalone/ folder was created yesterday to avoid conflicts 🤔 Are you sure it would create conflicts to merge it?

[drichards-87]

@Julio-Guerra I took a closer look at the PR and think it’s safe to merge without any concern about merge conflicts. I added one suggestion to use ASM, since the product name changes won’t be live until Monday. I will go ahead and commit the change and then merge the PR after the build job checks finish running.

[drichards-87]

/merge

[dd-devflow]

View all feedbacks in Devflow UI.

2025-04-10 23:03:18 UTC ℹ️ Start processing command /merge

---

2025-04-10 23:03:24 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-04-10 23:07:10 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 18m (p90).

---

2025-04-10 23:25:54 UTC ℹ️ MergeQueue: This merge request was merged