Common custom fingerprint rules

[4ekki]

Problem Statement

I have several microservices on my project. All of them can face some specific network errors and I want these errors to be processed in the same way. In order to not mix these specific errors with other network errors, I need to add custom fingerprint rules. However, I have to add the same rule explicitly into each project in Sentry, which looks weird.

Need ability to specify custom fingerprint rules for multiple projects somehow.

Solution Brainstorm

No response

Product Area

Processing

[linear]

ENG-5836

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[roggenkemper]

However, I have to add the same rule explicitly into each project in Sentry, which looks weird.

Do you mind elaborated on how adding the rule is weird? Is it inconvenient to add the same rule to each project or is there a bug when trying to do so?

[4ekki]

@roggenkemper, inconvenient. Let's say I have 20 microservices. It's very cumbersome to store same rules in 20 different places. Adding/removing rules in such case becomes very complicated.
Having some share rule set would solve my issue. Let's say there is some basic set of rules stored on organization level and on projects level it's possible to extend that basic list with project-specific rules