In another option, we can also bypass certain high priority users from filters, even if they meet the filter criteria. The bypass option should be used very cautiously, as bypass is not applied at the rule level.
DBC user is always bypassed.
Another way to use the filter option in a cautioned way is to use it under the warning mode. This will check the queries for filter rules and, based on the rule met, instead of aborting, it will only give a warning. These queries will be recorded in the DBQL table. Admins can plot the data against the incoming request and the warning it is creating. If you find that the number of warnings is high, it means high impact work is coming into the system. But it is also recommended to check ...
