*This epic groups all epics that are required to move the Error Tracking category from `minimal` to `viable`. The DESCRIPTION of this epic is a summary of the full [Opportunity Canvas](https://app.mural.co/t/gitlab2474/m/gitlab2474/1568925801645/71e7e6352180a1492a19a3d3ed6f96d48fefd597). Please reference the canvas for a full evaluation of this project.* ## Use Cases * PRIMARY: Customers currently using Sentry to track errors* * SECONDARY: Customers who are not using an tool to track errors* *We are conducting a survey to identify tools in use for GitLab's customer base ## Problems to Solve * Tracking work tickets in multiple tools is tedious * Review of error lists is manual, must be done frequently, and requires a certain level of innate context * Errors are noisy and it is takes a lot of time to review them ## Why are we using Sentry? Sentry is an open source error tracking tool that is the most widely used error tracking platform in market (this insight was found via a survey, results [here](https://gitlab.com/gitlab-org/uxr_insights/-/issues/1077)). Integrating with an open source tool enables us to bring this product offering to market much faster than if we built it greenfield. ## Business Case User priority is low. We do not have customer requests for this category. Current implementation of Error tracking in Sentry is too minimal for us to have engaged sufficient users to gather feedback. We need to improve usability and add functionality to the integrated workflow in order to validate if this desired by our customers. Business priority is high as investment in this category is necessary to achieve breadth as single app for the devops lifecycle. I am advocating for 2 milestones of investment to mature this category to the point of viable usability. ## What does success look like 1. Usage ping for the following metrics increase: * Instances with Sentry enabled * Instances creating issues from errors * Clusters with Sentry deployed 2. Broad adoption internally 3. Leveraging Pendo to track user behavior paths 3. Positive Anecdotal feedback and ideas ## Headline **"Correlate errors and merge request for fast resolution"** ## Supporting Evidence Please see https://gitlab.com/gitlab-org/gitlab/issues/31924 for supporting research. User interviews were conducted across a pool varying in role, tenure in career, and from companies of various sizes. Results and key takeaways have been summarized in this [Affinity Map](https://app.mural.co/t/gitlab2474/m/gitlab2474/1569970123837/7c6e021957163878082373760c6c3cd00419eb35).