Tagging and filtering Debug Symbols in Sentry
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
The customer would like to request an enhancement to how debug symbols are managed in Sentry. Specifically, it would be extremely useful to have the ability to tag debug symbols at the time of upload via the Sentry CLI. This would make it much easier to distinguish symbols associated with different versions or builds of an application.
In addition, having UI support to view and filter debug symbols based on these tags would greatly improve the debugging workflow, especially when dealing with multiple environments or releases. Being able to quickly locate the relevant symbols would save time and reduce potential confusion during issue investigation.
Contributor guide
Research direction
No files, tests, or entry points are named. First clarify the CLI upload-tagging model and the UI views and filters required, then identify the relevant Sentry components; done should include tagging during upload and viewing and filtering debug symbols by those tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100