docs(profiling): Updated page and added info on browser profiling configs #16111
+156
−55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
sfanahata
force-pushed
the
docs/browser-profiling-header-examples
branch
from
96a7340 to
5225050
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
platform-includes/profiling/automatic-instrumentation-headers/_default.mdx
Show resolved
Hide resolved
… browser profiling page - Add header config examples for Vercel, Netlify, Express, Nginx, Apache, CloudFront - Reorganize browser profiling page for better scannability - Add 'Quick Setup' section with clear 1-2-3 steps - Replace prose with tables for profiling modes and Sentry vs DevTools comparison - Move troubleshooting to collapsible section - Remove redundant explanations and tighten copy - Add warning for users who can't modify headers
sfanahata
force-pushed
the
docs/browser-profiling-header-examples
branch
from
5225050 to
0c50ddc
Compare
sfanahata
changed the title
sergical
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Document-Policy: js-profilingheader across common hosting platforms and servers.Preview: https://sentry-docs-git-docs-browser-profiling-header-examples.sentry.dev/platforms/javascript/guides/react/profiling/
Problem
Frontend developers often don't have direct control over server headers. The previous documentation simply said "configure your server to send this header" without providing platform-specific guidance, creating a significant barrier to enabling browser profiling.
Solution
Removed excess text to streamline the page
Added expandable sections with ready-to-use examples for:
vercel.jsonnetlify.tomland_headersfile.htaccesswith mod_headersAlso added a warning for users whose hosting providers don't support custom headers, directing them to backend profiling as an alternative.
Related
Part of React SDK documentation modernization project
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: