[DOCS-15308] Add definitions for iOS RUM view memoryAverage/memoryMax - #39670
Open
melamos wants to merge 1 commit into
Open
[DOCS-15308] Add definitions for iOS RUM view memoryAverage/memoryMax#39670melamos wants to merge 1 commit into
melamos wants to merge 1 commit into
Conversation
github-actions
Bot
added
Architecture
melamos
marked this pull request as ready for review
September 2, 2026 15:46
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-15308
Adds public definitions for the iOS RUM view
memoryAverage/memoryMaxattributes, following the same pattern used for the Androidview.memory_average/view.memory_maxattributes (RUM-17548). Explains what memory is measured, how the SDK calculates it, the default sampling frequency, and configuration options.Flutter's
memoryAverage/memoryMaxvalues are forwarded from the underlying native iOS/Android SDK rather than computed independently, and the Flutter Data Collected page already defers to the iOS/Android pages for event-specific attributes, so no separate Flutter page update is needed.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
Drafted with Claude Code: researched iOS/Flutter SDK source to confirm exact memory-attribute semantics, then wrote the doc update.
Additional notes
Semantics were derived from reading
dd-sdk-iossource directly (VitalMemoryReader.swift,VitalInfoSampler.swift,RUMViewScope.swift), not yet confirmed with Engineering. Per the ticket, this should be posted to #rum-mobile and reviewed by Rosa before merging.