Error: maximum recursion depth exceeded when adding multiple filters to Metric alert

[rodolfoBee]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Create a metric alert
2. Add filters to the alert logic (in this case 75).
3. Add a new filter

Expected Result

The filter is applied to the data used to trigger the filter

Actual Result

When the 76th filter is added the graph runs into an error:

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

[getsantry]

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

[ceorourke]

I'll put this in our backlog, maybe we need to have a hard limit on the number of filters here. Would the list of error_related_activity is possibly be shorter?

[volodymyr-ya-MA]

Hi, for our needs list should be longer) But if it's not possible, we will think about another solution.

[volodymyr-ya-MA]

If wildcards could be added to the list filter, we could potentially reduce the number of keys to just one. Previously, we had a separate list for each label, but with 200+ labels, the query began to take too long to load. To address this, we started using wildcards.
However, according to the documentation, it's not currently possible to use wildcards in combination with lists. As a workaround, we switched to using key/value pairs, but this introduced new issues when dealing with 75+ key/value pairs.

[volodymyr-ya-MA]

Okay, i see the issue about that:
#80597