timeseries [5/6] RUM-13949 Wire timeseries collection into RUM session lifecycle

[satween]

What does this PR do?

Connects the standalone pipeline and public configuration API to the existing RUM session lifecycle, completing the end-to-end data flow from configuration through to event emission.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

[satween]

• timeseries [6/6] RUM-13949 Add end-to-end timeseries verification tests with CSV fixtures #3436
• timeseries [5/6] RUM-13949 Wire timeseries collection into RUM session lifecycle #3435 👈 (View in Graphite)
• timeseries [4/6] RUM-13949 Add memory timeseries serializer and session factory #3434
• timeseries [3/6] RUM-13949: Add CPU timeseries data-point reader and serializer #3433
• timeseries [2/6] RUM-13949: Implement timeseries pipeline infrastructure #3432
• timeseries RUM-13949: Add timeseries JSON schemas and regenerate API surface #3431
• feature/timeseries

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 81.81818% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.40%. Comparing base (5ad5017) to head (af31b3d).

Files with missing lines	Patch %	Lines
...lin/com/datadog/android/rum/internal/RumFeature.kt	89.33%	7 Missing and 1 partial ⚠️
...ternal/timeseries/serializer/CpuEventSerializer.kt	20.00%	0 Missing and 4 partials ⚠️
...nal/timeseries/serializer/MemoryEventSerializer.kt	0.00%	0 Missing and 4 partials ⚠️
.../android/rum/internal/monitor/DatadogRumMonitor.kt	50.00%	2 Missing ⚠️
.../android/rum/timeseries/TimeseriesConfiguration.kt	66.67%	2 Missing ⚠️

Additional details and impacted files

@@                  Coverage Diff                   @@
##           feature/timeseries    #3435      +/-   ##
======================================================
+ Coverage               72.39%   72.40%   +0.01%     
======================================================
  Files                     977      977              
  Lines                   35820    35895      +75     
  Branches                 5970     5983      +13     
======================================================
+ Hits                    25930    25987      +57     
- Misses                   8268     8278      +10     
- Partials                 1622     1630       +8     

Files with missing lines	Coverage Δ
...rum/src/main/kotlin/com/datadog/android/rum/Rum.kt	86.25% <100.00%> (+0.17%)	⬆️
...kotlin/com/datadog/android/rum/RumConfiguration.kt	92.47% <100.00%> (+0.17%)	⬆️
...d/rum/internal/domain/scope/RumApplicationScope.kt	94.57% <100.00%> (-0.66%)	⬇️
...droid/rum/internal/domain/scope/RumSessionScope.kt	91.81% <100.00%> (ø)
...m/internal/timeseries/RumSessionScopeTimeseries.kt	93.75% <100.00%> (ø)
...nal/timeseries/RumSessionScopeTimeseriesFactory.kt	100.00% <100.00%> (ø)
.../android/rum/internal/monitor/DatadogRumMonitor.kt	85.92% <50.00%> (-0.63%)	⬇️
.../android/rum/timeseries/TimeseriesConfiguration.kt	90.91% <66.67%> (-9.09%)	⬇️
...ternal/timeseries/serializer/CpuEventSerializer.kt	86.54% <20.00%> (-9.54%)	⬇️
...nal/timeseries/serializer/MemoryEventSerializer.kt	87.72% <0.00%> (-5.14%)	⬇️
... and 1 more

... and 39 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[satween]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af31b3d917

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[satween]

all notes will be fixed in sepatate branch

[aleksandr-gringauz]

tbh, I find it hard to believe that there will be a situation that the total available RAM will be 0.

Should we just simplify and forget about this edge case? What will break?

[satween]

if by some reason totalRam return 0 - it would lead to ArithmeticException. Timeserices's RAM collector would be trying to collect some values, then would fail on percentage calculation so basically would do some useless job

[aleksandr-gringauz]

Could you explain how is this change related to the topic of this PR? is FPSVitalListener used in time series somehow?

[satween]

FPSVitalListener is enabled when vital frequency != NEVER. In the old logic a vitalScheduler was created iff frequency != NEVER. But with timeseries we also using vitalScheduler so it should be created if frequency != NEVER or timeseriesConfiguration != null. So why this changes was made