search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.19k stars 4.2k forks source link

Provide a way to test changing fingerprinting rules #41590

Open eric opened 2 years ago

eric commented 2 years ago

Problem Statement

I need to add some issue grouping fingerprinting rules to improve the grouping. I have to:

  1. save a change
  2. reprocess a bunch of events (burn my quota to do this)
  3. wait for that to complete
  4. confirm if this did what I wanted
  5. adjust the grouping
  6. save the change
  7. reprocess a bunch of events (burn my quota to do this)
  8. wait for that to complete
  9. confirm if this did what I wanted
  10. ...

Solution Brainstorm

It would be nice to have a way to preview what my changes would do to my events and see if that is actually what I wanted to have happen.

getsentry-release commented 1 year ago

Routing to @getsentry/ingest for triage. ⏲️

github-actions[bot] commented 1 year ago

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

jan-auer commented 1 year ago

Sorry, this was not intended to be closed.

seanhoughton commented 3 weeks ago

It appears that you can only reprocess native crashes Reprocessing is intended to address symbolication problems and as a side effect also re-runs the fingerprinting rules. This means the workflow for testing fingerprinting changes is even more painful and risky in production for non-native projects. You have to make a change in production and then either wait for a new instance of the event to come through or use the API to spoof a new event.

Sentry has one primary job - group sequences of error events into useful buckets. Fingerprinting rules are complex and can have dramatic effects on the behavior of the product - not having any way to safely test changes baffles me. The lack of attention to features related to this key area is surprising.

As an enterprise customer I consider this to be a major problem with the product. Poor grouping is the biggest complaint we get with users.