React Native Error Troubleshooting with Sentry | Scribe

    React Native Error Troubleshooting with Sentry

    • Jay Revels |
    • 0 step |
    • 2 minutes
    **React Native Project - Errors Marked in Red. Performance issues marked in blue.** **Sentry Groups issues by best in class fingerprint - a unique way to identity an event with information like stacktrace, message name.  Sentry automatically groups issues with similar characteristics.  For errors only, you can set up custom fingerprint rules under Project > Settings > Issue Groupings > Fingerprint Rules**
    **Sentry’s search provides you with reserved keywords like “is”, “user”, “serve”, and “browser” that you can use to search on the properties of issues, events, replays, and releases.  You can also create custom tags to which to search.   You can create custom tags by going to Project > Settings > Tags > add custom tag.** 
    **Sentry allows you to save searches for later use.   Name your searches so you can easily pinpoint issues that are important to you.  Save the search so only you can see it or expose it to the organization.** 
    **If Sentry is instrumented in both the front end and back end, the trace navigator allows you to see the distributed trace between the front and backend and any correlated errors.** 
    **The span view we have the operations breakdown - shows you how much time was spent in each operations within a transaction – the breakdown is operation type, duration, and percentage of the total duration.**
    **Filter by operation to drill into where the slow operation is. See how these operations and services are interacting to by using the waterfall chart.**
    **Sentry shows you the line of code and gives you critical context data with tags to help you quickly find cause of the problem.**
    **Click on the Github link and immediately find the problem code in the correct code repository.**
    **For web projects Sentry session replay shows you a video like reproduction of the user session so you can see what the user experienced before, during or after an error or performance issue.** 
    **Breadcrumbs provide a history and timeline leading up to an event and are totally customizable. Easily filter by operation so you can drill down to determine which operations impacted the core issue.**
    **Sentry transaction summary suggestions what spans and events that have the greatest impact on performance.**
    **The transaction summary includes a list of suspect spans that correspond to where most of the time in a transaction is spent.**
    **For web projects, Compare your site and page performance to Google standards - LCP, FCP, FID, and CLS. Receive a Good, Meh, or Poor rating.**
    Was this Scribe helpful?
    Save this document for future reference.
    This Scribe is in tip-top shape!Leave feedback if there are any issues with this Scribe