Inconsistent Resource Duration Timings in Datadog RUM Dashboard

[kagrawal98]

Describe the bug

Description:

We are currently using DdRum.startView and DdRum.stopView methods to capture views in our application. These methods also record resources, actions, and logs occurring within the view's duration. However, upon reviewing the data in the Datadog RUM dashboard, we noticed inconsistencies in the resource duration timings. The recorded durations appear inaccurate and do not align with the actual resource timings observed during the view span.

Impact:

This inconsistency affects the reliability of our performance metrics and hinders our ability to make informed decisions based on the data.

Actual Behavior:

The recorded resource durations in the Datadog RUM dashboard are inconsistent and do not match the expected timings.

Environment Details:

Datadog SDK Version: 2.4.3 Platform: iOS/Android Framework: React native - 0.73.9 Testing Device/Environment: Iphone 15 Simulator Attachments:

Link to Datadog RUM Dashboard for reference

Request:

Could you please help investigate this issue and identify the root cause? If needed, we can provide additional data or insights to assist in debugging.

Thank you for your support!

Reproduction steps

• Use DdRum.startView to begin capturing a view.
• Perform resource-intensive actions within the view (e.g., API calls or UI updates).
• Use DdRum.stopView to end the view span.
• Check the resource duration data in the Datadog RUM dashboard.

SDK logs

No response

Expected behavior

Resource durations recorded during the view span should accurately reflect the time taken for each resource.

Affected SDK versions

2.4.3

Latest working SDK version

It was working as expected previously as well

Did you confirm if the latest SDK version fixes the bug?

No

Integration Methods

NPM

React Native Version

0.73.9

Package.json Contents

No response

iOS Setup

No response

Android Setup

No response

Device Information

No response

Other relevant information

No response

[sbarrio]

Hi!, apologies for the late reply on this 🙇

Are you still seeing this issue? If you do, could you please contact the support channel so we can properly investigate you particular case?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity and has the awaiting-response label.

It will be closed if no further activity occurs within 3 days.