There’s never a good time for errors or performance degradations to show up, but during periods of peak traffic like the holidays, it’s especially critical to get immediate answers about what's failing and how to fix it.
The logic powering suspect commits has been updated to more accurately identify the cause of your issues.
Instead of only looking at the top frame of an issue, Sentry now checks the entirety of your stack trace to identify suspect commits. Because upstream code changes often cause downstream errors, you should encounter more accurate suspect commits.
Another way that we've increased the accuracy is by ignoring old commits. Only commits less than a year old will be eligible to be the suspect commit.
To learn more about this feature or learn how to set up suspect commits for your organization, read our docs. If you have feedback, we'd love to hear it in this GitHub discussion!
Github
Slack
Javascript
Python
React
Laravel
Next.js