Join us for a live demo on Wed. Dec. 11: Debugging Salesforce Apex Applications with Error Monitoring. Register Today!
February 12th, 2020 • By Mehak Garg and Ramon Niebla
At Rollbar, we care about reducing the time it takes developers to find and fix errors. This is why we’re making our integration with GitHub even stronger to provide more context around errors and reduce the mean time it takes to resolve them MTTR.
Last year, we launched Code Context to show additional lines of code within each frame of the stack trace, reducing the back and forth between GitHub and Rollbar. Now, we’re excited to support git blame to help you identify the last person to write or edit the line of code that caused the error, directly within the Rollbar UI.
Let’s say a new error pops up in Rollbar that you would like to investigate. As you click on the Traceback in the Item details page, you can see the exact line of the code that caused the error in each frame of the stack trace directly within the Rollbar UI.
Now, you may want to get more context on who should be assigned to the error or why some changes to the code were made. You don’t have to go to GitHub anymore to get this information. You can directly see the GitHub User Avatar of the last person to edit the offending line of code in Rollbar. If you hover over the Avatar, you can directly visit the pull request and the commit for that code. No more switching back and forth between Rollbar and GitHub!
In a nutshell, you can -
While ‘git blame’ might suggest you can blame someone and go about your work, we strongly recommend using it for getting more context on the code and assigning someone to the error when it makes sense.
In the example above, we can see at a glance in the first trace that the line of code that caused the error was written by Jon. However, after looking at the pull request and commit information, we notice that that code is performing as it should, and the problem is stemming from Jon's code getting incorrect values - in this case, an empty list - from a different part of the code, which we see when we expand the third frame.
We have enough information to say that we should improve the code that was passing the incorrect or missing data as well as edit Jon's code to be able to handle such cases.
We hope you find this new addition useful to your workflow! With a single click you can get the context you need to help you debug faster.