docs(rum): add Browser SDK v6 to v7 upgrade guide#36214
Open
thomas-lebeau wants to merge 7 commits intomasterfrom
Open
docs(rum): add Browser SDK v6 to v7 upgrade guide#36214thomas-lebeau wants to merge 7 commits intomasterfrom
thomas-lebeau wants to merge 7 commits intomasterfrom
Conversation
- Document breaking changes for Core, RUM, Logs, and Session Replay - Cover session manager rewrite, new privacy defaults, removed options, and API changes for v7 migration
Contributor
Preview links (active after the
|
- Add new section explaining how to update CDN bundle URL from v6 to v7 - Clarify that the crossorigin attribute goes on the script tag
- Update reference [28] to point to the datadoghq.dev RumInitConfiguration interface page for more detailed parameter documentation
- Replace temporal words (now, previously) with explicit v7 references per Vale style rules - Clarify action name computation strategy description - Rename Session Replay section to reflect data format change rather than serialization algorithm
Contributor
|
Added an editorial card: DOCS-14156 |
5 tasks
thomas-lebeau
added a commit
to DataDog/browser-sdk
that referenced
this pull request
Apr 24, 2026
Content has been moved to the documentation repo: DataDog/documentation#36214
- Mention the upgrade-browser-sdk-v7 skill to help automate migration steps
thomas-lebeau
commented
Apr 24, 2026
BenoitZugmeyer
approved these changes
Apr 28, 2026
BeltranBulbarellaDD
approved these changes
Apr 29, 2026
rgaignault
approved these changes
Apr 29, 2026
- Replace "better" with "sensible" for defaultPrivacyLevel description - Clarify enablePrivacyForActionName guidance to note upcoming build plugin masking capabilities
BenoitZugmeyer
approved these changes
Apr 29, 2026
rtrieu
requested changes
Apr 29, 2026
Contributor
rtrieu
left a comment
rtrieu
left a comment
There was a problem hiding this comment.
hi @thomas-lebeau thanks for this PR! i left some suggestions mainly for clarity and consistency with our style guide.
one thing i'd like to ask is that we leave the [28] link to point at the internal reference, but can you create a follow up PR to update it with the v7 parameters?
| [25]: /real_user_monitoring/correlate_with_other_telemetry/apm#opentelemetry-support | ||
| [27]: /real_user_monitoring/guide/proxy-rum-data | ||
| [28]: /real_user_monitoring/application_monitoring/browser/setup/#initialization-parameters | ||
| [28]: https://datadoghq.dev/browser-sdk/interfaces/_datadog_browser-rum.RumInitConfiguration.html |
Contributor
There was a problem hiding this comment.
this will take users to the external reference. can we keep /real_user_monitoring/application_monitoring/browser/setup/#initialization-parameters but open a different PR to update it with v7 parameters?
Contributor
Author
There was a problem hiding this comment.
This page does not contain an #initialization-parameters section. I did not follow the closely everything but the list of all initialization options have been removed from the documentation website a while back in favor of an automatically generated API documentation.
This is the same link used in the 3rd step in Manual client-side setup
Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
What does this PR do? What is the motivation?
Adds a new upgrade guide covering the Browser SDK v6 to v7 migration.
Merge instructions
Merge readiness:
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
Used Claude Code to draft the upgrade guide content.
Additional notes