New option to reverse stack traces in Crash Reporting
Posted Dec 12, 2024 | 2 min. (337 words)This enhancement is part of Raygun’s 12 Days of Christmas 2024. Over the past few weeks, we’ve shared daily updates on bug fixes and feature improvements inspired by feedback from you, our customers. These are the small but impactful changes you’ve asked for, designed to make Raygun faster and easier to use. Merry Christmas and thanks for following along—we’re excited to keep enhancing the tools you rely on!
Our special thanks to Pete from New York City who suggested this great idea!
What is it?
We’ve added a new option in Raygun Crash Reporting to reverse the order of stack traces in the app. Now you can customize how stack traces are displayed to suit your workflow and preference. This feature is compatible with Raygun’s GitHub and Azure DevOps integrations as well as the Copy stack trace button.
Where is it and how does it work?
To use this feature, open any error group from the Crash Reporting page. Click the options gear icon in the Summary or Error Details tabs, and toggle the ‘Reverse stacktrace’ option. Done!
Where can I learn more?
You can find further details about the Reverse stacktrace option in our documentation.
We hope you’ve enjoyed our 12 Days of Christmas and please let us know your thoughts—we love to learn and improve.
Merry Christmas from all of us at Raygun 🎄
Other 12 Days of Christmas improvements:
- Day 1 - New host filter for Real User Monitoring
- Day 2 - New API endpoint to delete all source maps
- Day 3 - Split your projects in Azure DevOps
- Day 4 - Auto-provisioning support for SAML SSO
- Day 5 - .NET error grouper V8
- Day 6 - New API endpoints for deployments
- Day 7 - New NOT operator for Raygun Alerting
- Day 8 - Raygun’s Christmas Bug Bashapalooza
- Day 9 - New URL tester for Real User Monitoring’s path segment rules
- Day 10 - New copy stack trace button for Crash Reporting
- Day 11 - New API endpoint to add comments to error groups
