Detail view of Sentry error in GitLab
Problem to solve
We want to display pertinent details of Sentry errors in GitLab to reduce time spent switching tools and context. Users will be fixing the error via GitLab, so as much review and work as we can keep in GitLab's interface, the more seamless we can make resolution. The goal of this MVC is to provide the user with enough pertinent information so that they can make a decision about what to do with the error - ignore it? triage it for later? fix it right away?
We will avoid completely rebuilding errors in GitLab as this has already been done in Sentry and focus on simplifying the triage/resolution process.
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
This work supports the Error Tracking Vision.
There will be 2 ways to view an error:
- List view - Errors appear in a list and show only top-level details
- Detail view - This access by clicking on the title of an error in the list. It opens in a new tab and displays details of the Error.
Design is detailed in the following section.
In terms of the work required for this specific issue, we are looking at the following:
|Remove external link from error title||Clicking error title opens new error detail page|
We're suggesting that clicking the error title from the list will now open up an error detail page. At a minimum, this detail page will include:
- A link to the Sentry error (which will open in a new tab if clicked)
- Error title and description
In addition, we can explore if any of the following pieces of information can be added:
- Information about when the error first occurred and last occurred
- A link to the file where the error occurred
- Links to "suspect commits" associated with the error
It's likely that the stack trace will be out of scope for this iteration but, added in a simple code block section as a basic formatting option should such information be easily available. The "new issue" button on the error detail page is also out-of-scope for this issue. It will be added as part of #33847
Permissions and Security
Documentation required, most likely here.