Adapt RUM server onboarding to include httpd

[pablomartinezbernardo]

What does this PR do? What is the motivation?

• Add instructions on how to onboard with injection in the server for RUM
• Small changes in the already existing content for clarity

Merge instructions

Merge readiness:

• Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then 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/pmartinez/rum-httpd/real_user_monitoring/browser/setup/server

[allspain]

Does HTTPD support allowedTracingUrls and excludedActivityUrls? If so we should edit the NGINX line to include HTTPD

[allspain]

There's a paragraph towards the bottom of the page that says:

Content compression by upstream server: If NGINX is acting as a proxy and the upstream server has content compression (like gzip, zstd, or Brotli) enabled, the module may not inject RUM. Ensure that content compression is disabled on the upstream server and configure NGINX to compress the content.

Should this be just NGINX or any of the webservers?

[rtrieu]

Created DOCS-10037 for more in-depth review.

[pablomartinezbernardo]

There's a paragraph towards the bottom of the page that says:

Content compression by upstream server: If NGINX is acting as a proxy and the upstream server has content compression (like gzip, zstd, or Brotli) enabled, the module may not inject RUM. Ensure that content compression is disabled on the upstream server and configure NGINX to compress the content.

Should this be just NGINX or any of the webservers?

It applies to all because they can all be configured as reverse proxies. It also feels redundant with the section above that reads "If proxying compressed traffic...". WGDYT @rtrieu ?

[rtrieu]

Some minor feedback for your review. But otherwise looks good!

[rtrieu]

There's a paragraph towards the bottom of the page that says:
Content compression by upstream server: If NGINX is acting as a proxy and the upstream server has content compression (like gzip, zstd, or Brotli) enabled, the module may not inject RUM. Ensure that content compression is disabled on the upstream server and configure NGINX to compress the content.
Should this be just NGINX or any of the webservers?

It applies to all because they can all be configured as reverse proxies. It also feels redundant with the section above that reads "If proxying compressed traffic...". WGDYT @rtrieu ?

I think you are right that this is repetitive. I'll push a commit with a suggestion to reconcile these two.

[dmehala]

Few suggestions. Thank you @rtrieu.

[rtrieu]

/merge

[dd-devflow]

View all feedbacks in Devflow UI.
2025-02-20 16:01:12 UTC ℹ️ Start processing command /merge

---

2025-02-20 16:01:21 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-02-20 16:18:14 UTC ℹ️ MergeQueue: merge request added to the queue

The median merge time in master is 7m.

---

2025-02-20 16:27:10 UTC ℹ️ MergeQueue: This merge request was merged