-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Auto-Instrumentation UI thread #36
Conversation
Since somebody asked if this info should go under the transaction or span, I believe the span makes more sense. |
Co-authored-by: Dhiogo Brustolin <dhiogorb@gmail.com>
In order to be consistent with getsentry/rfcs#36
- Introduce the file io on main thread performance problem. Not hooking up the options or anything yet. Just want to get the main core of the code ready to go first - I think this won't actually create any of the file io perf problems yet since the option is only added to default.py with 0 - Depends on getsentry/rfcs#36
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.
This looks very good!
Add new
blocked_main_thread
attribute to thedata
key-value map of theSpan
interface, indicating whether an auto-instrumented span has run its entire duration on the UI/Main thread.Rendered RFC