Out of the box, Sentry notifies you about crashes in your JavaScript apps and gives you useful tools to help you debug what your app was doing when it broke. If Sentry stopped there, it would still be great and valuable, but it’s possible to maximize your front-end debugging potential with just a few manual optimizations.
We get it — errors suck. And you don’t want to spend too much of your time fixing them, dealing with them, investigating them, etc. In our Workflow blog post series, we’ll help you optimize your, well, workflow from crash to resolution.
Epsagon helps troubleshoot serverless applications. Sentry helps monitor and fix crashes in real time. In this post, Raz Lotan, Software Engineer at Epsagon, uncovers how both tools blend to make the perfect workflow for debugging serverless applications.
Remember that time Mom told you that the internet is a dangerous place? No? Well, she did, but you weren’t listening. Jokes aside, we can probably all agree that there are many potential security risks in web services, with all their APIs and user-contributed content. Yet, the internet is what defines our digital age, and barely any piece of technology can do without. In the midst of this insecurity, Rust came along with its memory safety and zero-cost abstractions.
Sentry will be at AWS re:Invent on November 26 through 30 in Las Vegas. We hope to see you there! Unless you’re not going, in which case we hope to see you somewhere else at a different time. There are a couple of ways to meet with us at re:Invent...
When constructing a SaaS application, it’s easy to begin in the wrong place — namely, with architecture. Focusing first on software or architecture seems appealing because everyone is doing it, but trust me, you don’t actually want to start there.
Sentry introduced (welcomed) support for minidump crash reports earlier this year. In this post, Tim Fish, an essential contributor and co-maintainer of Sentry’s Electron SDK, explores his own experience with the intersection of minidumps and Electron.
