Symbolication Status overview & improvements
Open
Nobody has claimed this yet.
Waiting for: Product Owner
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
Right now it's quite complicated to find and understand if and why Symbolication failed in Sentry UI. There are several reasons for it:
- Some errors are hidden behind UI buttons and hovers
User cases:
Solution Brainstorm
There are several improvements we could make to address all 3 issues above:
- Make loaded images queryable attributes/tags.
- Make symbolication status queryable
- Based on that create extended UI to show list of all potentially problematic Images, and allow users to "mute/ignore" them - not showing errors and failures in the UI anymore. Additionally show users all issues that had non-ignored symbolication failures
- Extend the Issues UI to showcase these failures and resolution steps properly + add ignore buttons there as well
Product Area
Issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the two linked user cases and inspecting the existing Issues UI behavior described in the screenshots. The issue presents several brainstormed directions rather than a single scoped change, so completion criteria and the specific files or tests to update still need to be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100