search

getsentry / sentry

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

Fingerprint on message value using wildcard doesn't appear to impact grouping (on a long string) #54574

Open quickstark opened 1 year ago

quickstark commented 1 year ago

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Need an Issue with a long message (650+ bytes).

  1. Add Fingerprint rule: message:"*Failed to establish a new connection: [Errno 111] Connection refused*" -> connection-error
  2. Ingest events
  3. Check if grouping is applied

Additional Context: In the Event Grouping Details, the default grouping is a bit different than the message: Failed to establish a new connection: [Errno <int>] Connection refused'

Expected Result

Should expect all events with the stated string to be grouped.

Actual Result

Individual issues are still being created after the Fingerprint Rule was added.

Product Area

Issues

Link

Being submitted by Dirk N (Sentry EE) on behalf of a customer. Can share Org internally.

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

getsantry[bot] commented 1 year ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 1 year ago

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

lobsterkatie commented 4 months ago

@quickstark - Interesting. Looks like the parameterization is causing the problem.

This isn't a solution-solution, but can you please run your test again, substituting a * for the 111 in your fingerprint rule? In the meantime, I'll solicit opinions on potentially carving out a parameterization exception for Errorno xxx.

lobsterkatie commented 4 months ago

@quickstark - Interesting. Looks like the parameterization is causing the problem.

This isn't a solution-solution, but can you please run your test again, substituting a * for the 111 in your fingerprint rule? In the meantime, I'll solicit opinions on potentially carving out a parameterization exception for Errorno xxx.

Actually, I'm not sure this is the problem. I'd still love to know the results of the above test, but can you also please try using error.value:"*Failed to establish a new connection: [Errno 111] Connection refused*" -> connection-error rather than message:...?