Jump directly from a Sentry Issue to a breakpoint on the line that caused the error without restarting, redeploying, or adding more code.
See the docsAfter identifying the location of an error, Sentry prompts you to debug the issue — live, in production — in Rookout. With a click of a button, you’ll see the same line of code highlighted in Rookout’s IDE-like interface.
In Rookout, you can set “non-breaking breakpoints” and trigger the error again to receive real-time debug data in the context of the problematic code snippet. Why let the error happen all its own when you can trigger it yourself? Show that error who’s the boss.
Just look at all the high-quality security
features all accounts get, regardless of plan.
Here’s a quick look at how Sentry handles your personal information (PII).
×We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII:
If you have any questions or concerns about your privacy at Sentry, please email us at [email protected].
If you are a California resident, see our Supplemental notice.