[1A] Ignore Sentry errors from in GitLab on the error detail page
Problem to solve
Errors are noisy and plentiful which makes triage processes time-consuming because it is difficult to sort through the cruft to find the critical ones. By providing the ability to ignore an error in the GitLab UI, we give users another tool to clear out errors that don't need attention, allowing them to easily focus on the one's that require fixing. Ignoring non-critical errors makes the error list easy to scan and triage.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
This work supports the Error Tracking Vision.
Original Proposal
Add the option to ignore Sentry errors in GitLab. It should be available on the detail page for this issue.
There is a great discussion regarding implementation of the ignore feature in this comment.
| Design |
|---|
 |
- When the user clicks
ignorefrom the error detail page, they will be redirected to the error tracking list page, where the ignored error no longer shows up on the list. - Our default "ignore" behavior will follow Sentry's: "ignore indefinitely"
- Ideally, the "ignore" functionality will work in both directions (ie, will account for both the
User ignores error in Sentry -> Error automatically shows ignored status in GitLabandUser ignores error in GitLab -> Error automatically shows ignored status in Sentryuse cases)
Permissions and Security
Documentation
Documentation required. Please add a new section to the [Error Tracking docs].(https://docs.gitlab.com/ee/user/project/operations/error_tracking.html) called Taking Action on Errors