Crashes are something we know a thing or two about. We see a lot of reasons why apps crash, but we also see when a lot of popular mobile apps crash at once, that’s something we notice. Crashes across many mobile apps at the same time is not typically a result of an app-specific code update. I mean, there’s a non zero chance that hundreds of developers published broken apps… but these widespread issues are likely a result of two things.

Among developers, alerts have a bad rep. But outside the coding environment, alerts can signify positive developments. For example, a microwave just alerted me that my burrito is ready to eat. Sentry’s new Metric Alerts is the microwave to the frozen burrito that is your code.

Over the past week, we rolled out access to Advanced Data Scrubbing for all users. If you were one of our Early Adopters, you’ve known about this for a couple of months. As the name implies, it’s an addition to our existing server-side data scrubbing features, meant to provide greater control and more tools to help you choose which data to redact from events. One of Sentry’s main selling points as an error monitoring platform is the data it collects and aggregates.

App Nouveau is a Canadian professional services company that builds transportation management system software. As developers of highly-specialized software solutions, App Nouveau needs a robust error monitoring tool to deliver world-class code required by its commercial clients. App Nouveau recently began using Sentry to uplevel a few key areas in the code development lifecycle. Chief Technical Officer Paito Anderson and his team decided to switch to Sentry just a few months ago.

Zac Propersi, Engineering Manager at Sentry, can tell when a page is not loading as fast as it should — just by looking at it. While working on our new Metric Alerts feature, Zac noticed that the alerts pages were rendering slowly. Being the super Sentry user that he is, he wrote a custom query in Discover to see just how slow the transactions were.

Since the beginning, Sentry has adopted SemVer (semantic versioning) for all of its open source releases — major versions indicated breaking, backward-incompatible changes; minor versions meant new features, and patch releases were bug fixes only. This process worked fine for a long time. As the open source project evolved and grew into Sentry.io – our SaaS offering – the development team switched to a continuous delivery model.

Once an app is launched to market, it’s up to the engineering team to ensure that it continues to meet its SLAs. See how we use VMware Tanzu Observability (Wavefront) and Sentry to proactively monitor and fix issues before they become production problems. Every engineering leader has experienced the anxiety and stress of taking an app to production. It’s a mix of excitement and trepidation – your creation will be used in real life, but what if something goes wrong?