Editing Fingerprint Rules and Stack Trace Rules should show a preview of which issues will be affected

[jboulter11]

Problem Statement

Adding or editing a fingerprint rule is a serious exercise of guess and check. It's super unpleasant to try and add something, wait and see if it worked or not, then repeat until it finally works the way you want. Some of these rules are really impactful, and can re-bucket a lot of issues. They're not something you want to play around with blindly.

The same thing also applies to the Stack Trace Rules. It's hard to know for sure if you're doing the correct thing. I'd say the pain is more acute on Fingerprint rules though.

Solution Brainstorm

Ideally I'd like to see a discover-like interface specific to these fingerprint rules so I can get an idea for what my exact syntax (since it's different in some ways than discover) is going to do. I'd like to be able to see the existing buckets and also, ideally, what the new buckets might look like.

Similar to how alerts show a preview of which issues would trigger it, except it should actually work. In my experience almost all the alerts I've written the previews don't work.

Product Area

Issues

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[leeandher]

@jboulter11 Thanks for writing in, this makes a lot of sense. The UX around updating fingerprints and stack trace rules could definitely use some attention, and this seems like a reasonable ask to reduce friction around this feature. I will share it with the team, and see how we can prioritize this.