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.

Sentry started out as an Open Source side project in 2008. Today we are a Fair Source company with 100,000+ organizations on our SaaS and $100M+ ARR, but we have not forgotten our roots nor the hundreds of Open Source maintainers whose work we depend on for our success. Every year we share our success with the community, and 2024 is no different. This year, our budget is $750,000, up 50% from last year. We have 129 engineers right now, so that works out to $5,813 per developer on staff.

At Sentry, we don't just build debugging tools for developers—we use them ourselves. This story demonstrates how we leveraged our own platform to solve a mysterious performance issue that was causing significant latency spikes in our critical infrastructure which is used in nearly every backend request.

Application performance is critical for a seamless user experience, but all too often, developers find themselves struggling to pinpoint slowdowns. Understanding the root cause is the first step to diagnosing and solving performance issues. In this article, we’ll explore six common root causes of application performance slowdowns and share actionable advice on how to fix them. We will also show how platforms like Sentry can help uncover, trace, and debug these issues faster.

TL;DR: The Sentry extension for GitHub Copilot now goes beyond chat to help you generate tests, surface issues, and suggests fixes all within your regular PR workflow. Did you forget to write unit tests? Automatically generate them and merge them to your feature branch within GitHub. Have you already merged a PR? Catch new issues, get solutions to those bugs, and deploy those fixes quickly. Add the Sentry extension from the GitHub Marketplace to get started. Continue reading for more details and demos.