OverOps’ new integration with GitLab and GitHub empowers development teams to assign every error to the right developer responsible for fixing it.

We’re excited to share that we’ve expanded our collaboration with GitLab and GitHub to support git blame and automated source attach! Read the PR announcement here.

OverOps’ mission is to help application development and SRE teams deliver more reliable software, faster. But the truth is, the software development pipeline is too complex to allow for a single product to deliver on this promise all on its own. This is why one of the most frequent requests we received from our customers over the years was to integrate their code repositories with OverOps.

Today, we’re excited to meet this demand by allowing OverOps, GitLab, and GitHub users to easily identify who last committed an offending line of code and who last edited the source file it resides in.

One of our beta users for this launch, an engineering manager at a large U.S. Insurance company, told us that operating without this would be like going back to the dark ages. We couldn’t have said it better ourselves!

Introducing the OverOps integration with GitLab and GitHub

By integrating OverOps with your code repository, your development team will be empowered to embraces a “you code it, you own it” mentality, allowing them to:

  • See who was the last author who changed the code across the call stack of each error.
  • Link errors to commits and view the latest code changes directly in your git repository.
  • Assign every new and critical issue to the right developer responsible for fixing it.
  • Capture rich error snapshots with the source code and variable state for every error.

Get Deep, Code-Level Context to Quickly Resolve Any Error

Let’s quickly walk through an example scenario. The team has just released a new version for your backend Java application. All tests have passed, and no outstanding issues were identified in staging. The logs look okay, your APM is not reporting any issues, and then… OverOps identifies a new swallowed NullPointerException that prevents your users from completing a key business transaction.

With this new integration, you’ll not only receive a snapshot of the exact variable and environment state at the moment of error, but you’ll also be able to see who committed the new code change that introduced it, allowing you to easily assign it to them for quick resolution.

Seamless Setup with Automated Source Attach

Before our automated source attach feature was released, the default way to view source code within OverOps was to either allow us to decompile your code, or manually point OverOps to the location of your source files.

With the new source attach capability, we can now automatically pull the original source code directly from your code repositories, including your comments and corresponding line numbers in each error’s analysis within OverOps.

Getting down to the code-level root cause of new exceptions and errors just got a lot easier.

We’re just getting started

Integrating git blame data into the OverOps code view and error analysis is just the beginning. Now that git blame data is accessible within OverOps, we’re already thinking about all the new and exciting things you’ll be able to do with it. Gamifying exceptions with team leaderboards is just one of the options that were suggested so far, and we can’t wait to see what our customers will be doing with this data going forward.

To learn more about the OverOps support for git blame and automated source attach, register to attend a live webinar, where we’ll demo the git blame integration, covering best practices and processes for building a culture of accountability.

Can’t wait to try it yourself? Send us an email to hello@overops.com and we’ll help get you started.

Alex Zhitnitsky

Alex is the Director of Product Marketing at OverOps. As an engineer-turned-marketer, he is passionate about transforming complex topics into simple narratives and using his experience to help software engineering navigate their way through the crowded DevOps landscape.


Leave a Reply

Your email address will not be published. Required fields are marked *