If an error occurs on your website, and you weren’t there to log it, did it happen?
Well, yes. It did. But even if you decided to start logging such errors, you’d learn something really quickly: logging JavaScript errors is hard.
In this talk from JSConf Uruguay, Sentry VP of Engineering Ben Vinegar discusses the state of client-side JavaScript error logging in 2016, covering topics like:
At the end of this talk, you’ll have all the information you need to get started logging your own client-side errors. And even if you use a 3rd-party service/client library to do it for you instead, you’ll have a better handle on how those tools work under the hood.
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.