Symbolication Status overview & improvements

[mujacica]

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:

1. Some errors are hidden behind UI buttons and hovers

2. Some "errors" are expected, getting users to ignore them all the time (e.g. external overlays/plugins loaded into the app, where users don't control symbols at all) 3. Even when able to identify what the issue is, it's extremely hard for users to figure out and understand what the resolution is (e.g. what do I do with a timeout, can I upload symbols, reprocessing is hidden) 4. Loaded images are not queryable and/or searchable - preventing users to find all issues that contain or don't contain specific image loaded

User cases:

• Allow searching and filtering issues by which modules were loaded at the time of the crash #122955
• No org-level view of symbolication failures, and no bulk path to reprocess once symbols are fixed #122956

Solution Brainstorm

There are several improvements we could make to address all 3 issues above:

1. Make loaded images queryable attributes/tags.
2. Make symbolication status queryable
3. 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
4. Extend the Issues UI to showcase these failures and resolution steps properly + add ignore buttons there as well

Product Area

Issues

[linear-code]

ENG-8518

[default300]

Would love this ❤️