Blog Open Source Streamline and shorten error remediation with Sentry’s new GitLab integration
Published on: January 25, 2019
3 min read

Streamline and shorten error remediation with Sentry’s new GitLab integration

Your code has bugs, my code has bugs, everyone’s code has bugs (probably). Let’s fix that.


Sentry is open source error tracking that gives visibility across your entire stack and provides the details you need to fix bugs, ASAP. Because the only thing better than visibility and details is more visibility and details, Sentry improved their GitLab integration by adding release and commit tracking as well as suspect commits.

Streamline your workflow with issue management and creation

When you receive an alert about an error, the last thing you want to do is to jump around 20 different tools trying to find out exactly what happened and where. Developers with both Sentry and GitLab in their application lifecycle benefit from issue management and issue creation to their GitLab accounts directly in the Sentry UI, alleviating some of the hassle of back-and-forth tool toggling.

GitLab account in Sentry

Of course, less tool jumping results in a more streamlined triaging process and shortened time to issue resolution – something that benefits the whole team.

Creating GitLab issue

Have a GitLab issue that wasn’t created in Sentry? No problem. Existing issues are also easily linked.

Import GitLab issue

Find and fix bugs faster with release and commit tracking

Why stop at streamlining the triaging process, when we can also make issue resolution more efficient? Sentry’s GitLab integration now utilizes GitLab commits to find and fix bugs faster.

With the newly added release and commit tracking, an enhanced release overview page uncovers new and resolved issues, files changed, and authors. Developers can also resolve issues via commit messages or merge requests, see suggested assignees for issues, and receive detailed deploy emails.

Want a big flashing arrow that points to an error’s root cause? Sentry’s suspect commits feature exposes the commit that likely introduced an error as well as the developer who wrote the broken code.

Suspect commits feature

Keep in mind that this feature is available for Sentry users on “Teams” plans and above.

Check out Sentry’s GitLab integration documentation to get started.

What’s next?

Again, why stop there, when we can do even more? GitLab is currently working to bring Sentry into the GitLab interface. Soon, GitLab and Sentry users will see their Sentry errors listed in their GitLab projects. Read the documentation on the integration here.

About the guest author

Eva Sasson is a Product Marketer at, an open source error-tracking tool that gives developers the contextual information they need to resolve issues quickly, and integrates with the other development tools across the stack.

We want to hear from you

Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum. Share your feedback

Ready to get started?

See what your team could do with a unified DevSecOps Platform.

Get free trial

New to GitLab and not sure where to start?

Get started guide

Learn about what GitLab can do for your team

Talk to an expert