Document Node.js profiler ability to use uploaded source maps

[szegedi]

What does this PR do? What is the motivation?

I'm documenting the ability for the Node.js profiler to use uploaded source maps.
As a minor edit, I'm also moving the optional steps to the end of the list of steps (in this case, reversing the orders of steps 4 and 5, so 5 and 6 are now the optional ones.)

Note for reviewers:

The link for source map uploads points to a page in the RUM guide, as that's the one that discusses source map uploading. While this is a minimal edit that can link to that documentation from profiler documentation, it raises few questions:

• Should we mention Node.js profiling in the RUM guide page, similar to how it mentions Error Tracking and Browers Log Collection as other consumers of the data?
• Should we otherwise edit that RUM guide and/or move the source maps upload to a more generic place?

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass 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.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/szegedi/nodejs-profiler-sourcemaps/profiler/enabling/nodejs

[domalessi]

Left a few suggestions! Let me know if you have any Qs. Otherwise, apply those fixes and we should be good to go.

[domalessi]

Suggested change

	4. A couple of minutes after you start your application, your profiles appear on the [APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][9] guide.
	4. A couple of minutes after you start your application, your profiles appear on the [APM > Profiler page][5]. If they do not, see the [Troubleshooting][9] guide.

[domalessi]

Suggested change

	6. Optional: [Upload Source Maps][10] (in Preview.) If you use source maps and you deploy them with your application the profiler will read them and produce mapped locations in profiles. Source maps in `.map` files as well as inline source maps are both supported. If you want to reduce deployment sizes (typically in serverless environments) you can choose to not deploy source maps and instead upload them to Datadog. You need to use dd-trace version 5.93.0 or newer for uploaded source maps to work, and your deployed source files still must contain the `@sourceMappingURL` annotation as an indication that they need to be mapped using the uploaded maps.
	6. Optional: [Upload Source Maps][10] (Preview). If you use source maps, the profiler reads them and produces mapped locations in profiles. Source maps in `.map` files and inline source maps are both supported. To reduce deployment sizes (for example, in serverless environments), you can choose not to deploy source maps and instead upload them to Datadog.
	**Note**: Uploaded source maps require dd-trace version 5.93.0 or newer. Your deployed source files must also contain the `@sourceMappingURL` annotation so the profiler knows to use the uploaded maps.