...
- Try to determine how to reproduce the error on staging:
- Watch Fullstory if available
- ExampleSee section on Fullstory below
- Check for api request : Under the exception trace, you may see an exact api request
- Open each line in the exception trace to see if there is a clear indicator of a failure on a specific value as an issueExamplefield
- Example: https://sentry.io/sighten/production/issues/426038336/
- The example above shows that the field "ssn" has a specific pattern "[^0-9+]" that is not met. This can then be communicated to the user in order to allow them to move forward.
- Watch Fullstory if available
- When finished checking, mark in some way indicating reviewed
...
Many Sentry errors give you a direct link to Fullstory. This allows you to watch the exact actions of the user when the error happens. The Fullstory URL can be found in the sentry error page by finding the "Cookies" section and retrieving the "fs_uid" (the highlighted section of the uid can be placed in a fullstory URL).
Example:https://www.fullstory.com/ui/1chQ/session/5687485698932736:5647791397273600
This will take you to the BEGINNING of a fullstory session, which will NOT be the exact time of the error. To find the error, you can do the following:
- Try to match up the timestamps. For example, if the sentry error occurred at 5:10pm PT and the Fullstory starts at 4:55pmPT, then fastforward 15 minutes and you should find the error.
- Scan throw the entire video on 4x speed until you find the errors
Jira
All Sentry errors automatically create a ticket in the Jira Sentry (SEN) project : https://sighten.atlassian.net/projects/SEN/issues. Our goal is to have 0 open issues in this project.
...