Problem Statement

We are currently having lots of false-ish positives from N+1 detection (with Django). We have multiple loops that we iterate over a queryset, make internal - external calls, update data on related tables, send notifications etc. Sentry detects them as N+1, which is technically true, but also there is no feasible way for us to solve them and we are perfectly happy with those loops.

Sentry has several settings about how N+1s are detected, but there is nothing that equivalent of # noqa

Solution Brainstorm

Sentry should support a # noqa style selective disabling mechanism for N+1 issue detection.