Operations | Monitoring | ITSM | DevOps | Cloud

We’re expanding beyond just code coverage and added a suite of new capabilities to help you break production less: AI PR Review, AI Test Generation, Test Analytics, and Bundle Analysis.

Optimizing app performance can be challenging, even for seasoned developers. Frontends groan under the weight of bloated assets, backends lag from sluggish database queries, and mobile screens freeze at the worst times. But it doesn’t have to be that way. Sentry’s latest update brings domain-specific views to Insights & Profiling, giving developers the clarity they need to solve issues quickly.

What if you could not only find software issues you care about but also have the fix ready? We just introduced several updates that intelligently group new issues, reducing noise by about 40% and automatically suggesting fixes to annoying bugs you shouldn’t have to think about.

Whether it’s sitting through a meeting that should’ve been an email or reading a blog post written by AI – no one enjoys losing time they’ll never get back. That’s why we rolled out updates to help you fix problems faster while skipping the manual grind, including smarter search, customizable issue views, real-time uptime alerts, and Session Replay for Mobile.

The Sentry Unity SDK has been effective for crash reporting, including: We are confident that we have the best crash-reporting solution out there. Now we were looking towards offering some out-of-the-box insights into the game’s performance. Right out of the gate, we hit the first question: What would auto-instrumentation for Unity games look like?

This post is part of our debugging series, where we share tricky challenges and solutions while building Sentry. On March 4th, 2024, the most metal incident happened - INC-666 INC-666, in a nutshell, was where the issue alert rule post-processing step was flooded with more load than it could handle, and alerts that were supposed to have fired did not. This means that Sentry customers might not be receiving alerts if the query that would have triggered the alert is rate-limited.