Introducing Annotated Stacktraces

When things break, your first questions are typically: Why is this happening now? What changed? Who knows about these changes?

At Opbeat, we’ve have experienced this often enough to make us wonder:
How can we make it faster to debug errors?

This is what we came up with.

Starting today, new apps on Opbeat will have stacktraces annotated with the authors of the lines of code. It looks like this:

Annotated Stacktraces

This immediately tells you who on your team might know something about what is going on.

Additionally, Opbeat shows you the release in which each line was modified and when it went into production. This tells you exactly when things started to break.

We call it Annotated Stacktraces but you may recognize it as the output from git blame.

As Opbeat already integrates with GitHub, there is no additional setup steps required and new apps created on Opbeat will have it baked in.

We will be rolling out this update for existing users over the next couple of days.

About the author
Ron Cohen is co-founder and CTO at Opbeat. A founding member of Django Copenhagen, Ron enjoys sharing his experiences with code and ops around the world.
You can follow him on Twitter or GitHub.