RUM-12923: Attach RUM information on profiling event

[ambushwork]

What does this PR do?

This PR attaches following RUM context information in Profiling event so that it can be shown as tags in profiling page:

• session id
• vital id
• view name
• view id
  Also it changes the timing of RUM feature send TTID event to Profiling feature in order to stop the recording, so that the profiling event can attach the real first view event instead of artificial "AppLaunch" view event.

Motivation

RUM-12923

Demo

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)

[ambushwork]

application id + view id

[datadog-official]

🎯 Code Coverage
• Patch Coverage: 68.52%
• Total Coverage: 71.38% (-0.03%)

View detailed report

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 729c7ff | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[codecov-commenter]

Codecov Report

❌ Patch coverage is 60.78431% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.21%. Comparing base (3d91afb) to head (965c1b2).
⚠️ Report is 6 commits behind head on feature/perfetto-profiling.

Files with missing lines	Patch %	Lines
.../internal/startup/RumSessionScopeStartupManager.kt	30.00%	6 Missing and 1 partial ⚠️
...src/main/java/com/datadog/android/rum/TTIDEvent.kt	0.00%	6 Missing ⚠️
.../android/profiling/internal/ProfilingDataWriter.kt	80.00%	0 Missing and 4 partials ⚠️
...dog/android/profiling/internal/ProfilingFeature.kt	70.00%	3 Missing ⚠️

Additional details and impacted files

@@                      Coverage Diff                       @@
##           feature/perfetto-profiling    #3017      +/-   ##
==============================================================
- Coverage                       71.25%   71.21%   -0.04%     
==============================================================
  Files                             874      875       +1     
  Lines                           31768    31810      +42     
  Branches                         5321     5326       +5     
==============================================================
+ Hits                            22636    22653      +17     
- Misses                           7626     7644      +18     
- Partials                         1506     1513       +7     

Files with missing lines	Coverage Δ
...dog/android/profiling/internal/ProfilingContext.kt	100.00% <100.00%> (ø)
...lin/com/datadog/android/rum/internal/RumFeature.kt	89.42% <ø> (+0.19%)	⬆️
...ernal/domain/scope/RumVitalAppLaunchEventHelper.kt	88.42% <100.00%> (ø)
...dog/android/profiling/internal/ProfilingFeature.kt	84.62% <70.00%> (-2.05%)	⬇️
.../android/profiling/internal/ProfilingDataWriter.kt	91.07% <80.00%> (-6.43%)	⬇️
...src/main/java/com/datadog/android/rum/TTIDEvent.kt	0.00% <0.00%> (ø)
.../internal/startup/RumSessionScopeStartupManager.kt	87.78% <30.00%> (-7.22%)	⬇️

... and 41 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[0xnm]

For now, if we don't have TTIDEvent, we shouldn't even write profile and upload it.

I guess the goal is to have only profiles with RUM context associated.

[ambushwork]

in previous dogfooding, all the profiles > 1min are probably the profiles without correct TTID signal, if we stop sending them, we won't be able to see these kinds of abnormal profiles in next dogfooding.

[0xnm]

all the profiles > 1min are probably the profiles without correct TTID signal

I don't think it is a problem of TTID signal, but rather a problem of Perfetto callback result delayed.

But we can keep it if you suggest it is valuable to have such, we just need to remove that before the GA.

[ambushwork]

yes I agree, my point is that we need to keep it for exposing the perfetto callback issue

[ambushwork]

/merge

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2025-11-21 11:26:45 UTC ℹ️ Start processing command /merge

---

2025-11-21 11:26:51 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-11-21 11:39:19 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in feature/perfetto-profiling is approximately 0s (p90).

---

2025-11-21 11:43:29 UTC ℹ️ MergeQueue: This merge request was already merged

This pull request was merged directly.