Operations | Monitoring | ITSM | DevOps | Cloud

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.

With January over, 2024 is in full swing. Read on below to find out more about the Metrics Alpha, Cron Monitoring GA, SDK improvements, and more.

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.

Imagine this: Your website is getting a lot of traffic and you have some kind of metrics, logging, or performance monitoring setup (maybe even Sentry). You’re alerted to something… odd. You open up your error and see that a request was interrupted by another request. Uh oh. This sounds like a user was rage-clicking , clicking like crazy making duplicate requests. You weren’t expecting that!

Sentry Cron Monitoring alerts you when your scheduled jobs fail and gives you the context you need to fix it - like we do with error and performance issues. Cron Monitoring focuses on serving code-level insights behind missed and failed jobs and relating them to errors already in your issue stream.

Sentry was born and bred in the Open Source community, and we very much think of ourselves as part of it today. One thing we’ve learned together over the years is that an over-emphasis on user freedom can come at the cost of developer sustainability, to the point that we are now in an Open Source sustainability crisis.

While companies tout the importance of user privacy, few put their money where their mouth is – or in our case, actually live and breathe the concept the way we do as a company. From how we think about our Product to the way we implement our Marketing, Sentry’s take on privacy is rooted in three key fundamentals: Don’t make me choose, think like your customer, and build for tomorrow today.

This is not another abstract post about what the ramifications of the cookieless future might be; Sentry actually removed cookies from our website a few months ago. Here’s how it impacted us positively and negatively, in both expected and unexpected ways. I hope this can serve as a guide or inspire others who are considering making this change.

Since enabling browser profiling on our Sentry.io dashboard a month ago, we have collected over 2M profiles and learned a lot about how our users experience our dashboard. The profiles collected gave us insight into how our dashboard performs in production and surfaced some issues causing UI jank. In this post, we will look at an example of an issue we discovered using Profiling.