Skip to content

Document Node.js profiler ability to use uploaded source maps #35801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
szegedi merged 7 commits into from
Apr 8, 2026
Merged

Document Node.js profiler ability to use uploaded source maps #35801

Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a9802e7
Add information on source map uploads
szegedi Apr 7, 2026
db11822
Move optional steps after the startup
szegedi Apr 7, 2026
9cf7dda
Apply suggestions from code review
szegedi Apr 8, 2026
13f47fa
Refine some wording to emphasize deployment
szegedi Apr 8, 2026
8d5d028
Apply suggestion from @domalessi
domalessi Apr 8, 2026
ff7a311
Apply suggestion from @domalessi
domalessi Apr 8, 2026
26be546
Apply suggestions from code review
szegedi Apr 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions content/en/profiler/enabling/nodejs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,9 +76,11 @@
{{% /tab %}}
{{< /tabs >}}

4. Optional: Set up [Source Code Integration][4] to connect your profiling data with your Git repositories.
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.

Check warning on line 79 in content/en/profiler/enabling/nodejs.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.words_case_insensitive 

Use 'see', 'read', or 'follow' instead of 'refer to'.

5. 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.
5. Optional: Set up [Source Code Integration][4] to connect your profiling data with your Git repositories.

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.

Check warning on line 83 in content/en/profiler/enabling/nodejs.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'will'.

## Not sure what to do next?

Expand All @@ -97,3 +99,4 @@
[7]: /profiler/enabling/supported_versions/
[8]: /serverless/aws_lambda/profiling/
[9]: /profiler/profiler_troubleshooting/nodejs/
[10]: /real_user_monitoring/guide/upload-javascript-source-maps/
Loading