You need to sign in or sign up before continuing.
Surface language and urgency information on Sentry error detail page
Problem to solve
Manual triage of errors is challenging because they are noisy and pertinent information is difficult to find. Based on research, we've decided to add additional information about errors to the detail page to help reduce context switching between GitLab and Sentry. This information includes language and urgency.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
This work supports the Error Tracking Vision.
Proposal
We need to figure out the information we get for an error from the Sentry API. Ideally, we can get language/framework and some sort of priority/severity.
| Design for surfacing the event level and language |
|---|
 |
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Sarah Waldner