-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feat] Anti log spam #11
Comments
Hi
Feel free to submit a PR to support this.
Regards,
|
i think we don't need to cache the error notification, because we need to fix the error as soon as possible |
I agree it would be a nice thing to have. That error could be muted for an hour and then popup again to avoid too much noise. |
I think the AntiLog Spam its great but need be a another package. |
Was just looking if someone already suggested log throttling 👍 |
true |
would be a nice feature since one error in a cronjob can trigger the spam but also good to know that its a critical bug that needs attention immediately. |
Add throttle option to log (use Cache / redis cache) to don't spam many time the same error
with 2 options : enabled, throttle time (default 3600 sec)
key is : md5(the error name, file name, and line number)
The text was updated successfully, but these errors were encountered: