Feature Request: Filter Breadcrumbs for all events for a ticket
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
We have data for one of the top crashes on Sentry, but the relevant details are only available in the breadcrumbs. The breadcrumbs, specifically the navigation entries, show the pages where the error occurred.
The challenge is that this issue is happening across multiple pages, and we want to prioritize fixing the pages where the issue occurs most frequently.
Here’s what I’ve tried so far:
Checked other parameters such as message, culprit, etc., but none of them contain useful data for this issue.
Tried to find a way to filter breadcrumbs across all events, but currently, Sentry does not provide such filtering capabilities.
Right now, Sentry allows breadcrumb filtering only for a single event.
Is there a way to extrapolate this filtering to all events so we can analyze and prioritize effectively? Also we need to filter the count of matching breadcrumb value.
**Example**
Suppose the navigation breadcrumbs show:
pageA in 10 events,
pageB in 20 events,
pageC in 30 events.
I want to directly filter and sort this data in descending order of count without having to manually open and review each event one by one.
This would help us quickly identify and prioritize the most impactful pages where the issue occurs most frequently, allowing for a more targeted and efficient fix.
### Solution Brainstorm
_No response_
### Product Area
Issues
Contributor guide
Research direction
The issue targets Sentry’s Issues product area and requests breadcrumb filtering across all events with counts. Start by locating the existing single-event breadcrumb filtering and the Issues query or aggregation entry points; the report names no files or tests. Done means users can filter navigation breadcrumbs across events and sort matching values by count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100