Operations | Monitoring | ITSM | DevOps | Cloud

Sentry

Prioritize Errors that Matter with Sentry + Jira Server

Bugs are dumb. They’re also inevitable. However annoying that may be, it’s more productive to accept the existence of bugs in our workflows than to panic-spiral every single time they pop up. Part of the acceptance process is keeping bugs (or at least the ones you care to fix) top of mind by paralleling your error monitoring and your sprint planning.

Using nginx and Sentry to Trace Errors to Logs

To quote the timeless Ren and Stimpy jingle, “everyone needs a log.” It’s true — everyone does need a log, especially developers. Despite the fact that no developer looks forward to combing through logs, they’re incredibly useful when unexpected performance issues, like one we recently had with file uploads, need some investigation.

Apply for Sentry's Open Source Grant

Work should be fun. Sometimes it’s not, especially when your full-time job isn’t aligned with something you care about — like open source. Contributing to open source full-time is an opportunity not available to everyone. We’d like to change that with the Sentry Open Source Grant, which offers funding to an individual dedicated to working on an open source project for three months.

Debug Tough Front-end Errors by Giving Sentry More Clues

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.