<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> <!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> TBD ### Problem to solve Replace the legacy, limited Errors UI with the flexible dashboard in GitLab Observability UI. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) ### User flow 1. Use Sentry SDK to send errors to GitLab 1. User can navigate to the errors interface (GitLab Observability UI) using the GitLab navigation 1. User can see a list of errors in GitLab. Errors can be sorted by Frequency, First Seen, or Last Seen. Users can also filter the error by error status and error title 1. User can click on an error in the error list to see the error details. The error details shows (TBD) 1. User can take the following action on the error details page - Create an issue, ignore the error, and resolve the error 1. User can also embed errors into any work items, including issues, epics, incidents, tasks, or MRs by pasting the URL of the error detail in a description or comment ### Proposal First iteration / MVC = `Error Tracking` page built using the GitLab Observability UI - On by default. - Shows a plain list of errors for the project, sorted by occurrence. - Uses an external Error Tracking data source (cloud or self-hosted Sentry) Further incremental additions: 1. Point the page to integrated Error Tracking instead of external data source 1. Filter errors with an input text field 1. Filter errors with dynamic metadata (e.g. environments) 1. Error Tracking page is defined as code and visible (read-only) 1. Error Tracking page is editable as code ### Further details We won't try to replicate what is in Sentry nor necessarily have a 1:1 replacement of the legacy Errors UI. Instead, we will determine the capability we can make available and enable a complete end-to-end workflow to deliver a completed product. ### Permissions and Security Developer role or above ### Documentation TBD ### Availability & Testing TBD ### Available Tier ~"GitLab Free" ### Feature Usage Metrics TBD ### What does success look like, and how can we measure that? TBD ### What is the competitive advantage or differentiation for this feature? 1. A complete error management system all within GitLab