getsentry / getsentry/sentry

Symbolication Status overview & improvements

Open
#123,111 2 comments 0 reactions 0 assignees View on GitHub

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:

  1. Some errors are hidden behind UI buttons and hovers
Image Image Image 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) Image 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:

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 failuresImage
  4. Extend the Issues UI to showcase these failures and resolution steps properly + add ignore buttons there as well
Image Image Image Image
Product Area

Issues

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.