getsentry / getsentry/sentry

Unable to search chained exceptions

Open
#86,473 3 comments 2 reactions 0 assignees View on GitHub
Bug Quality Sprint Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. Send an event with chained exceptions:
![Image](https://github.com/user-attachments/assets/ec345bfc-6388-45f1-ac6c-4c3ae963a6e1)

2. Search on the issues page for the chained exeption

### Expected Result

The issues page to find it

### Actual Result

If I search for the top exception `Error: Connecting to database failed.` I find the error:
![Image](https://github.com/user-attachments/assets/b3e399f6-7c46-4c6c-ae40-2b896d2dec24)

While searching for the chained error `LojaError: a new test error` nothing is found. The current workaround is to specify the search with `error.type:LojaError` or `error.value: a new test error`. The same is valid on the Discover page. This makes the search bar not useful and inconsistent for chained exception
![Image](https://github.com/user-attachments/assets/ddd6d783-78bf-4b0c-bc74-85099bf2b289)

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue by sending an event with chained exceptions, then search for the chained exception from the Issues page and Discover page. Trace the search handling for exception values and types, and compare it with the existing top-exception behavior. Done means an unqualified search for the chained error finds the event consistently in both locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.