-
Notifications
You must be signed in to change notification settings - Fork 14
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
[Sentry] Investigate what sentry reporting we can add for critical areas of the app #1448
Comments
I was able to spend a little bit of time on this on Friday and Monday. After reading through the docs and looking at the automatic transactions Sentry is capturing I think it's best to turn off automatic transaction recording docs. Sentry only records transactions for UIKit view controllers, which we don't use much, and it appears that a lot of the data it collects is misleading. For instance it starts a transaction when the user taps the Home tab but it doesn't complete it when the home feed displays data. We should set up custom instrumention as described above. We should add comprehensive breadcrumb tracking to help us understand and reproduce performance issues. Now that I understand more about how Sentry uses transactions, spans, and profiling I can start going through each of the cases above and see which can be measured by Sentry's tools. |
Here are the first few tickets I created. |
@setch-l I've filled out the ticket description with my proposal for tracking all of these, and moved the ticket to UAT for your review. Let me know if you have any concerns. Happy to talk about any of these in more detail either here or in a meeting. |
We have identified the following critical areas of the app:
Note these last 2 encompass content loading, profile loading & lists. Are there other things beyond those we need to be away of in these scenrios?
We need to ID sentry tracking for each of these critical areas of the app experience so we can easily identify when something has gone wrong.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: