If you’re reading this, it means you’re at least mildly interested in Sentry and would likely be interested in some exciting new features that we’ll be releasing very soon. You can get the details on all these new features below. Also, if you’re currently in our Early Adopter program, you can potentially access these features right now. Not part of this program? Your organization can opt in at any time with the flip of a single switch found in your org settings.

It’s February, which means it’s the perfect time for us to publish our 2018 year in review. Other organizations publish these in January or even December, and they are wrong to do so. February is the best month for this, except for those years when we publish it in March. 2016 was a big year for us. 2017 was even bigger. You know what that means: 2018 was the biggest yet. How big was it?

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. To quote “the second-most frequently quoted writer in The Oxford Dictionary of Quotations after Shakespeare,” Alexander Pope, “to err is human.” There will always be errors, even in code written by the best developers.

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.

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.

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.

On this episode of Exception Perceptions, Katy Farmer, InfluxData’s Developer Advocate, tells us all about Kubernetes (also known as K8s). Watch the episode, and then accompany Katy on her journey to uncover the “captain” of containerization’s secrets.

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.