[DOCS-10912] RUM View-Based Ownership #30056
Open
+45
−2
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
github-actions
bot
added
Images
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
hestonhoffman
approved these changes
Jun 20, 2025
github-actions
bot
added
Architecture
MaelNamNam
requested changes
Jul 1, 2025
|
|
||
| {{< img src="/real_user_monitoring/ownership_of_views/ownership-sessions-explorer-1.png" alt="View of Sessions Explorer, where you can filter user sessions based on the teams assigned in Team Ownership, making it easy to find replays relevant to your team." >}} | ||
|
|
||
| By default, the toggle is enabled, which filters metrics and event data to show only the views your team owns. If you belong to multiple teams, you can enable or disable specific team filters. The teams that own a view are also listed in the top-right corner of all event side panels. |
There was a problem hiding this comment.
Suggested change
| By default, the toggle is enabled, which filters metrics and event data to show only the views your team owns. If you belong to multiple teams, you can enable or disable specific team filters. The teams that own a view are also listed in the top-right corner of all event side panels. | |
| By default, the toggle is enabled, which filters metrics and event data to show only the one coming from views your team owns. If you belong to multiple teams, you can enable or disable specific team filters. The teams that own a view are also listed in the top-right corner of all event side panels. |
|
|
||
| ## Overview | ||
|
|
||
| Ownership of views lets you see only the RUM metrics and events for the parts of your application that your team is responsible for. After you've set up ownership of views, every RUM event and metric from those parts is **tagged** with your team's name. You can turn this filter on or off using the **My Teams** toggle on the Summary, Optimization, and Session Explorer pages. |
There was a problem hiding this comment.
Suggested change
| Ownership of views lets you see only the RUM metrics and events for the parts of your application that your team is responsible for. After you've set up ownership of views, every RUM event and metric from those parts is **tagged** with your team's name. You can turn this filter on or off using the **My Teams** toggle on the Summary, Optimization, and Session Explorer pages. | |
| Ownership of views lets you see only the RUM metrics and events for the parts of your application that your team is responsible for. After you've set up ownership of views, every RUM event and metric attached to those views is **tagged** with your team's name. You can turn this filter on or off using the **My Teams** toggle on the Summary, Optimization, and Session Explorer pages. |
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.
What does this PR do? What is the motivation?
Adds a new guide about View-Based Ownership in RUM
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.
Additional notes