You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find myself wanting grey listing every now and then. For example, some cron failures are due to temporarily failed DNS lookups every now and then and it's frequent enough to be annoying. But, if I whitelist it I won't see a situation where DNS fails constantly.
Proposal at a high level:
Add field to whitelist entries called rate limit or perhaps disable threshold?
rate limit would be X matches in Y time
if rate limit is tripped, stop applying the filter to subsequent messages
Benefit: I can whitelist something that fails every now and then by it's nature but still catch if it starts failing more then usual.
The text was updated successfully, but these errors were encountered:
Took a look at the triggers that perform whitelist filtering and I don't see a way to implement rules specific to a whitelist that wouldn't have a bad performance hit. In any case it would require a significant rework of core functionality. Sadly I don't think I have the skills for it.
I find myself wanting grey listing every now and then. For example, some cron failures are due to temporarily failed DNS lookups every now and then and it's frequent enough to be annoying. But, if I whitelist it I won't see a situation where DNS fails constantly.
Proposal at a high level:
Benefit: I can whitelist something that fails every now and then by it's nature but still catch if it starts failing more then usual.
The text was updated successfully, but these errors were encountered: