As it stands (for now) all results are processed and reported back to the admin of the system. A "threshold" system needs to be put in place to help reduce the noise from false positives.
These thresholds should be related to the Impact scores so that only runs (inline or the queued) that meet or are equal to the threshold have notifications sent.
Future idea: have thresholds/watches set on individual filters so that if they're tripped, the admin is notified regardless of if the total Impact level falls below the threshold.
As it stands (for now) all results are processed and reported back to the admin of the system. A "threshold" system needs to be put in place to help reduce the noise from false positives.
These thresholds should be related to the Impact scores so that only runs (inline or the queued) that meet or are equal to the threshold have notifications sent.
Future idea: have thresholds/watches set on individual filters so that if they're tripped, the admin is notified regardless of if the total Impact level falls below the threshold.