Get notified if a job is run too often about healthchecks HOT 3 OPEN

Thanks for suggestion!
I'm thinking of two scenarios where this might be useful:

1. Your cron job runs as it should (say, once a hour), but you've set up "Period" and "Grace" parameters incorrectly (say, once a day). It's not a huge issue except for when the check actually goes down, it will take longer (~23 hours) until you find out.
   In this situation a warning in the dashboard and possibly in the monthly report would be sufficient.
2. Your "Period" and "Grace" parameters are set up correctly, but something changes on the cron side (the job is e.g. looping infinitely and pinging on each iteration). In this case we would want to be proactive and send a notification.

Which one did you have in mind? Any ideas on how to distinguish between the two?

from healthchecks.

I was thinking about the second scenario. It probably has to be something you can turn on/off for a check, since you still want to support checks for jobs that run at irregular times (but you still want to be notified if it hasn't run within X time).

Perhaps a good solution would be to have the ability to specify "minimum time between runs"?

from healthchecks.

The minimum time between runs could either be defaulted to 0s, in which case it wouldn't solve scenario 1. Or, it could be defaulted to something like 75% of Period, and - in scenario 1 - it would then notify the user that the check had been pinged too frequently, and the user could then change the setting.

I think I'm leaning towards defaulting it to 0s, since it doesn't feel like core-functionality, and it's probably quite likely that users who are trying out the service for the first time would get the warning-notification when they access the check URLs using a browser or Curl.

from healthchecks.