-
-
Notifications
You must be signed in to change notification settings - Fork 352
fix: Don't create transactions for HTTP Requests #1237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Right now, SentryNetworkTracker only works with SentryUIPerformanceTracker. |
Codecov Report
@@ Coverage Diff @@
## master #1237 +/- ##
==========================================
+ Coverage 95.37% 95.55% +0.18%
==========================================
Files 148 148
Lines 5206 5215 +9
==========================================
+ Hits 4965 4983 +18
+ Misses 241 232 -9
Continue to review full report at Codecov.
|
Yes, I think if there is a span on the scope and |
…com/getsentry/sentry-cocoa into fix/dontcreatetransactionforrequest
So that's raise the question: if there is a UI transaction going on, but it is not in the scope because the user has attached something in the scope first. Which one should we use to create the request span, the UI transaction or the one in the scope? If we take Android in consideration, since they use only the scope to manage performance tracking, this request span should be added to the one in the scope right? |
I believe we should add the http span created as a child of whatever transaction is bound to the scope (and not any of its spans). |
I agreee. I think this makes sense. We can start with that because it's simple and we can do more complex stuff later. |
a820d79
to
2d64527
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, we should add a few more tests and then we are ready to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one more open comment. Thanks for adding the tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's address the comment about the removal of the observer somewhere else.
📜 Description
Prevent SentryNetworkTracker from creating a transaction if there is no active transaction in SentryPerformanceTracker.
💡 Motivation and Context
There should not be standalone transactions for HTTP requests
Fix #1216
💚 How did you test it?
Unit tests
📝 Checklist
🔮 Next steps