Summary
The Source Maps page describes source maps solely in the context of errors, stating: "Upload your source maps to Sentry to enable readable stack traces in your errors." However, the Profiling page explicitly calls out source maps as a benefit of Sentry Profiling (vs. Chrome DevTools):
Source maps — Deobfuscated function names (Sentry Profiling) vs. Minified names (Chrome DevTools)
This creates a documentation gap: a user setting up profiling who follows the source maps page would have no indication that source maps also apply to (and benefit) profiling data — deobfuscating function names in profiles, not just in error stack traces.
Scope
- Update the Source Maps page intro and/or description to reflect that source maps benefit both errors (stack traces) and profiling (function names).
- Optionally, add a cross-reference on the Profiling page pointing to the Source Maps setup docs.
- No change to actual SDK behavior — this is a docs-only clarification.
References
Action taken on behalf of Prithvi Rajakumar.
Summary
The Source Maps page describes source maps solely in the context of errors, stating: "Upload your source maps to Sentry to enable readable stack traces in your errors." However, the Profiling page explicitly calls out source maps as a benefit of Sentry Profiling (vs. Chrome DevTools):
This creates a documentation gap: a user setting up profiling who follows the source maps page would have no indication that source maps also apply to (and benefit) profiling data — deobfuscating function names in profiles, not just in error stack traces.
Scope
References
Action taken on behalf of Prithvi Rajakumar.