Gaps in a transaction's Trace View lead to very large, potentially inaccurate durations #12927
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
7.112.1
Framework Version
No response
Link to Sentry event
No response
SDK Setup/Reproduction Example
No response
Steps to Reproduce
No steps required on client's end. Sentry is instrumented and performance session data is captured accordingly.
Expected Result
If a performance transaction takes multiple hours or several minutes, it would be expected to get full insight into what exactly is contributing to the long duration. Even if it's thread blocking for example, identifying this for a potential performance issue would be insightful.
Actual Result
Because some transactions are missing span context, samples are being sent to Sentry that provide inaccurate findings. This can lead to outliers and askew averages for the transaction summaries and suspect spans.
