RUM-16696: Attach profiling context to the View events#3562
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feature/continuous-profiling #3562 +/- ##
================================================================
+ Coverage 72.46% 72.48% +0.01%
================================================================
Files 987 987
Lines 36595 36604 +9
Branches 6094 6096 +2
================================================================
+ Hits 26518 26529 +11
+ Misses 8414 8413 -1
+ Partials 1663 1662 -1
🚀 New features to boost your workflow:
|
| } | ||
| } | ||
|
|
||
| private fun resolveViewProfilingStatus(datadogContext: DatadogContext): ViewEvent.Profiling? { |
There was a problem hiding this comment.
Just to better understand.
What profiler run this status corresponds to? I mean there can be application launch profiling, continious profiling, 1 RUM session can have many of them (correct me if I am wrong here).
Is it the most recent one?
There was a problem hiding this comment.
ProfilingStatus represents if there is a profiling session on going - more specifically speaking - if a profiling session which is manually requested by SDK through ProfilingManager.requestProfiling is running, it means app launch profiling and continuous profiling will update this status, (they don't overlap since ProfilingManager doesn't support multiple profile sessions through request), but it doesn't include the trigger based profiling for ANR, which is a background profiler can run in parallel with our profiling session.
5 participants
What does this PR do?
Attach profiling context to the View events as we did for RUM Errors and Vitals
Motivation
RUM-16696
Review checklist (to be filled by reviewers)