Allow Fingerprint Rules to reference stack frames from handled errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
Handled errors (for example iOS NSError events) include a full stack trace in the event, and the frames are visible in the UI. However, Fingerprint Rules cannot reference those frames. {{ stack.function }} is empty for handled errors.
This prevents declarative grouping based on application-specific frames, so many handled errors with the same domain and code are grouped into a single issue even when their execution paths differ.
Solution Brainstorm
Allow Fingerprint Rules to reference the frame that actually reports the error. For example: {{ stack.function }} → the frame that reported the error
This would enable declarative fingerprinting based on application modules or functions without requiring SDK-side fingerprinting.
Product Area
Issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation file or test is named. Start by tracing Fingerprint Rules handling and how handled-error stack frames are represented, then identify the frame used for reporting errors. Done means {{ stack.function }} can reference that frame for handled errors and supports grouping by application-specific functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, python
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100