Skip to content

Fix the way we are recording the last interaction for ITNV metric#2431

Merged
mariusc83 merged 1 commit into
feature/view-loading-timesfrom
mconstantin/fix-the-way-we-record-last-interaction
Dec 6, 2024
Merged

Fix the way we are recording the last interaction for ITNV metric#2431
mariusc83 merged 1 commit into
feature/view-loading-timesfrom
mconstantin/fix-the-way-we-record-last-interaction

Conversation

@mariusc83

@mariusc83 mariusc83 commented Dec 5, 2024

Copy link
Copy Markdown
Member

What does this PR do?

The interval we consider for the interaction-to-next-view metric is the moment the last action finished on the previous view until the moment the new view was created. Based on the last discussion we decided to completely rely on the RUM ActionEvents that were sent as potential last interactions meaning that we had to do several changes in the RumActionScope by reporting more information in the ActionSent event to the RumViewScope.

Motivation

What inspired you to submit this pull request?

Additional Notes

Anything else we should know when reviewing?

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)

@mariusc83 mariusc83 self-assigned this Dec 5, 2024
@codecov-commenter

codecov-commenter commented Dec 5, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.03%. Comparing base (c6c77ea) to head (3a49cd0).
Report is 2 commits behind head on feature/view-loading-times.

Additional details and impacted files
@@                      Coverage Diff                       @@
##           feature/view-loading-times    #2431      +/-   ##
==============================================================
- Coverage                       70.04%   70.03%   -0.00%     
==============================================================
  Files                             775      775              
  Lines                           28694    28708      +14     
  Branches                         4809     4809              
==============================================================
+ Hits                            20096    20105       +9     
  Misses                           7276     7276              
- Partials                         1322     1327       +5     
Files with missing lines Coverage Δ
...ndroid/rum/internal/domain/scope/RumActionScope.kt 97.81% <100.00%> (+0.05%) ⬆️
...g/android/rum/internal/domain/scope/RumRawEvent.kt 100.00% <100.00%> (ø)
.../android/rum/internal/domain/scope/RumViewScope.kt 94.66% <100.00%> (-0.37%) ⬇️
...actiontonextview/ActionTypeInteractionValidator.kt 100.00% <100.00%> (ø)
...nteractiontonextview/InternalInteractionContext.kt 100.00% <100.00%> (ø)
.../android/rum/internal/monitor/DatadogRumMonitor.kt 85.67% <100.00%> (+0.09%) ⬆️
...tadog/android/rum/internal/monitor/StorageEvent.kt 90.00% <100.00%> (+4.29%) ⬆️
...ontonextview/PreviousViewLastInteractionContext.kt 100.00% <100.00%> (ø)

... and 24 files with indirect coverage changes

@mariusc83
mariusc83 force-pushed the mconstantin/fix-the-way-we-record-last-interaction branch from cbdf023 to 581338c Compare December 5, 2024 12:32
@mariusc83
mariusc83 marked this pull request as ready for review December 5, 2024 12:54
@mariusc83
mariusc83 requested review from a team as code owners December 5, 2024 12:54
@mariusc83
mariusc83 force-pushed the mconstantin/fix-the-way-we-record-last-interaction branch from 581338c to 3a49cd0 Compare December 5, 2024 13:15
@mariusc83
mariusc83 merged commit 426cd07 into feature/view-loading-times Dec 6, 2024
@mariusc83
mariusc83 deleted the mconstantin/fix-the-way-we-record-last-interaction branch December 6, 2024 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants