[actions][sentry] apply fingerprint rules to group issues better

[gutsytechster]

Sentry groups issues by the provided message argument in the implemented scenario. However, when the message includes a pattern recognizable by sentry defined here - https://github.com/getsentry/sentry/blob/master/src/sentry/grouping/parameterization.py#L56, values against these patterns are replaced with placeholders and aren't used to group issues.

E.g., if the sentry title contains hostnames with the same exception, the two would be grouped as below

Prashant Test Local | Development | Spider bookspider.com notification
Prashant Test Local | Development | Spider quotespider.com notification

grouped into

Prashant Test Local | Development | Spider <hostname> notification

This would be unintended behaviour, and we'd like to have the two spiders raise two different sentry alerts.

Providing spider's title to the fingerprint would ensure that the exact message is used to create fingerprints, and hence the two issues will have separate fingerprint values and eventually two different sentry issues.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.58%. Comparing base (d7d553a) to head (816186b).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #455      +/-   ##
==========================================
+ Coverage   79.54%   79.58%   +0.03%     
==========================================
  Files          76       76              
  Lines        3242     3242              
  Branches      539      539              
==========================================
+ Hits         2579     2580       +1     
  Misses        593      593              
+ Partials       70       69       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[muzaffaryousaf]

@gutsytechster were you able to test the changes ? Thanks.

[gutsytechster]

Hi @muzaffaryousaf

Yes. Here's a sentry alert that grouped events of the different domain alike spiders together. This was previous to fixes.

Here's how it grouped these events

After fixes, the two separate events were triggered for these two spiders - bookspider.com and quotespider.com

Here's how it grouped these events.

Notice Fingerprint values in these images, where issue title is used to group on top of the {{default}} values.

[gutsytechster]

After discussion with monitoring team, we'd like to categorize only based on the event title only, discarding the default grouping. It'll be unique for each spider and it will group all types of spidermon errors under the same issue.