Setting up Sentry Alerts based on an issue’s level is one of the most effective ways to filter out noisy notifications and receive notifications for high priority errors. Follow along to this demo to see how.
Want to know when a new issue in Sentry starts to become a problem? Learn how the New Issue Alert Rule can help you prioritize new errors that need your attention. Follow along to this demo to see how.
Based on our experience working with thousands of mobile developer teams, we developed a mobile monitoring maturity curve here at Sentry. We hypothesized that once teams achieved stability and were no longer firefighting and fixing crashes, they’d shift to streamlining workflows and eventually focus more on optimizing mobile app performance. In a recent workshop, we asked mobile devs where they fell on the curve. The results were surprising.
Breadcrumbs provide rich context about what steps your application and user took prior to an error. As this information isn’t captured in the stack trace, Breadcrumbs can be a game-changer for debugging your application.
As we celebrate the 10th anniversary of Sentry’s support for the.NET ecosystem with over 150 million downloads, we’re excited to announce Sentry.NET 4.0! Building on top of.NET 8.0, this major release includes many exciting new features, including support for Profiling, Metrics, AOT and trimming, native crash reporting, Spotlight, and better.NET MAUI support. Version 4 of the SDK is now available!
You may have noticed that the banners asking you to accept “cookies” whenever you visit a website have gotten bigger and more annoying over time, especially if you browse the internet in Europe. This is in response to laws and regulations that are meant to protect users from being tracked unless they agree to be tracked. The requirement in Europe is that if you want to use cookies, subject to a few narrow exceptions, the purposes must be disclosed with granularity and agreed to in detail.
Sentry now automatically monitors your top endpoints and functions for significant regressions. And alerts you when - and where - there’s a sudden slowdown. Check out how we resolved a specific regression that increased 3000%.
When I first had the idea for this post, I wanted to provide a collection of actionable ways to handle errors caused by API rate limits in your applications. But as it turns out, it’s not that straightforward (is it ever?). API rate limiting is a minefield, and at the time of writing, there are no published standards in terms of how to build and consume APIs that implement rate limiting.