Conversation
Adds a Timeseries section to Mobile Vitals covering the series collected, how to enable collection on each SDK, and where the graphs appear. Adds the corresponding configuration options to the iOS and Android advanced config partials, and describes the Performance Timeseries panel on the RUM Explorer and Operations pages.
github-actions
Bot
added
Architecture
Contributor
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
1 participant
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?
RUM Timeseries is going into public preview. The iOS and Android SDKs sample memory and CPU once per second across a session and graph the result in the Session, View, and Operation side panels. Today Mobile Vitals only reports CPU and memory as a per-view average, which hides spikes and gives no sense of when usage changed — this documents the new continuous view of the same two resources.
Changes:
## Timeseriessection on Mobile Vitals: series collected, how to enable per SDK, where the graphs appear.timeseries/setTimeseriesConfigurationentries in the iOS and Android advanced configuration partials.Merge readiness
Three things to resolve before this can merge:
https://www.datadoghq.com/product-preview/rum-timeseries/, which follows the existing slug convention but has not been confirmed to exist. Needs the real preview form URL.@_spi(Experimental). The documented Swift snippet omits the@_spi(Experimental) import DatadogRUMline, because the gate was added to keep the feature invisible during testing and is expected to come off for the preview. Until the SDK team removes the annotation, the snippet as written will not compile for customers. This is a release-ordering dependency, not a docs bug.AI assistance
Used Claude Code throughout: it synced the SDK and docs repos, read the timeseries implementation in dd-sdk-ios and dd-sdk-android and the panel components in web-ui to establish the API surface, units, sampling interval and UI labels, then drafted these changes. I directed the scope and reviewed the output.
Additional notes
Facts verified in source rather than inferred:
memory_footprint(kilobytes) andmemory_percent; CPU ascpu_usage, normalized across all cores.view: null. The panel scopes the session-wide series visually using start/end markers rather than filtering by view ID, which is why the copy says the graph "always covers the full session".Not covered here: localized copies under
content/{fr,es,ja,ko}/will drift, and no screenshot is included yet — happy to add one once the preview UI is stable.