Antiflood email

[dejurin]

In my opinion, a fair feature that will prevent flooding (spam).

For example, my job suddenly runs with an error, I get a report in the email. If my script runs every minute it can cause problems until I get access to the panel.

Having a checkbox can prevent mail from being sent again until the script runs with a different status.

[jhuckaby]

That's a great idea, thank you. Funny enough, my LogAlert system already does this very thing. I can probably just grab that code and port it over.

[dejurin]

I tested my build today, something went wrong, and I got flooded with mail. My Gmail limit of 500 messages was almost exhausted. ;-)

[jhuckaby]

Cronicle Version 0.9.76 was just released. It has a new feature:

https://github.com/jhuckaby/Cronicle/blob/master/docs/Configuration.md#max_emails_per_day

max_emails_per_day

You can optionally set a limit on the number of emails Cronicle will send per day. This is a simple "anti-flood" system, to prevent a repeating failing job from flooding your InBox, if you are not around to address it. Example:

"max_emails_per_day": 100

If the limit is exceeded, Cronicle will log an error for each subsequent send attempt. The counter resets at midnight server time.

[mikeTWC1984]

Speaking of limits/floods, there are few more scenarios for that

1. Some bad logging, when job printing some logs fast and limitless. I think there is some default limit for logsize, that will cause job abortion, right?

2. Jobs that triggers itself (self-chained or some API loop). If job will start crashing/exit quickly, it will get in a crazy cycle, running hundreds or thousand times a minute, and it's kinda hard to kill it. I'm pretty sure there is no default limit for that, but perhaps some hidden setting?

[jhuckaby]

Excellent ideas, thank you Mike!

Yes, Cronicle v1 has a job log max size, which will abort the job if the size is exceeded. This is configurable globally as a default, but also can be overridden at both the category and event levels.

As for self-triggering jobs, Orchestra does have a configurable limit on the number of jobs that can be spawned per minute. I can backport this to Cronicle v1 if there is enough interest.