[Issue Grouping] [Fingerprint Rules] Ability to disambiguate events by multiple stack.function matchers
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
Currently, if Fingerprint Rules attempts to disambiguate with multiple stack.functions, such as
stack.function:"AssetBundles" stack.function:"OutOfMemory" -> asset-bundle-caused-oom
stack.function:"OutOfMemory" -> general-oom
Only the 2nd one matches any events.
I would like to use Fingerprint Rules to disambiguate events by which set of functions that appear in the stack trace.
In my example case, it's to track how out out-of-memory crashes are caused by our Asset Bundles system.
I attempted to use the other matchers, but none of them serve this case. https://docs.sentry.io/concepts/data-management/event-grouping/fingerprint-rules/#matchers
Troubleshot this with Sentry support #215475403609089
Solution Brainstorm
No response
Product Area
Settings
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
Start with the fingerprint-rules matcher documentation linked in the issue and trace the existing handling of stack.function matchers. Reproduce the two-rule example with events containing both functions and only OutOfMemory, then verify that the intended disambiguation is reflected in grouping behavior and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100