TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Error Tracking

1 post · Jan 2019 – Jan 2020

What this trail covers

GitLab's error tracking feature is evolving from a minimal integration with Sentry to a more robust product. The current iteration focuses on enabling users to create GitLab issues directly from Sentry errors, pre-filled with relevant details. This is part of a larger strategy to improve error correlation, resolution, and triaging within the GitLab platform, moving towards a fully realized error tracking capability. This post details the integration of Sentry's release and commit tracking with GitLab, allowing for faster bug identification and resolution through suspect commits and enhanced release overviews.

All GitLab trails
  1. Why we scoped down to build up error trackingThis post details the iterative development process for the 'Create an Issue' button within GitLab's error tracking feature. It describes three frontend iterations: 1) a basic button leading to a blank issue, 2) pre-filled issue content with error details, and 3) a styled button with proper formatting and pre-filled context. It also mentions backend work to associate issues with errors and display existing issue links. The post highlights the benefits of frontend-first development and breaking down work into MVCs to increase MR rate.
  2. Sentry's GitLab integration streamlines error remediationThis post details the enhancement of the Sentry-GitLab integration to include release and commit tracking, and the 'suspect commits' feature. It explains how this streamlines the workflow by allowing issue creation and linking directly from Sentry to GitLab, and how commit data from GitLab can be used within Sentry to identify the root cause of errors and the responsible developer. It also mentions future work to bring Sentry errors directly into the GitLab interface.