You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checking the timing of each segment in WebTransaction view they each have almost the same timing and if you sum them together they exceed the Response time.
Here you can see all the segment from the graph have the same data (they are the same height everywhere).
But if only filtered for Response time it is way lower.
The breakdown table shows something similar
Expected Behavior
Each segment summed together doesn't exceed the Response time
Steps to Reproduce
I tried to do this with a fresh install on a brand new project and I couldn't reproduce the issue so it is a bit weird.
Your Environment
Python 3.8
Django 3.2.16
sentry-sdk 1.19.0
newrelic 8.8.0
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description
When checking the timing of each segment in WebTransaction view they each have almost the same timing and if you sum them together they exceed the
Response time
.Here you can see all the segment from the graph have the same data (they are the same height everywhere).
But if only filtered for Response time it is way lower.
The breakdown table shows something similar
Expected Behavior
Each segment summed together doesn't exceed the
Response time
Steps to Reproduce
I tried to do this with a fresh install on a brand new project and I couldn't reproduce the issue so it is a bit weird.
Your Environment
Python 3.8
Django 3.2.16
sentry-sdk 1.19.0
newrelic 8.8.0
Additional context
#755 might be related.
The text was updated successfully, but these errors were encountered: