[DOCS-15513] Update Flutter RUM documentation for Actions and Resources association - #39669
Open
rtrieu wants to merge 1 commit into
Open
[DOCS-15513] Update Flutter RUM documentation for Actions and Resources association#39669rtrieu wants to merge 1 commit into
rtrieu wants to merge 1 commit into
Conversation
Actions and manually reported Resources now properly associate with Errors and Actions in the latest SDK versions.
github-actions
Bot
added
Architecture
estherk15
approved these changes
Sep 2, 2026
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
2 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?
Fixes DOCS-15513
Removes an outdated Flutter Web limitation stating that Actions (
addAction) and manually reported Resources (startResource/stopResource) don't properly associate with Errors or Actions. This is no longer accurate in the latest SDK versions.Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Claude Code to identify the outdated limitation and update the docs.
Additional notes