It might surprise you that the version of cron that runs on your server today is largely compatible with the crontab spec written in the 1970s. One downside of this careful backwards compatibility is that jobs, even on the same server, can be created and scheduled differently.
Cron job failures create chaos for your users and your team. After analyzing over a million failure reports these 4 problems emerged as the most likely causes of preventable job failures.
Last year we introduced Field Agent, an important addition to your toolkit that gathers extra data on your critical tasks, packages it up, and radios it back to Dead Man's Snitch. Since then, we've been working on new ways to leverage the data that Field Agent collects to give you more insight into your Snitches and their failures.
We're excited to announce that Dead Man's Snitch is now easier to use with your entire team. Gone are the days of sharing a single login or using a shared mailing list for alerts. Now, everyone on your team can have their own login and personalized alert settings. Using Slack or PagerDuty and don't need emails? You can now opt out of email alerts as well.
Cron expression support has been the most requested feature, since the launch of healthchecks.io. Long story short, it’s been implemented and is ready to use! You can now set up a time-based schedule for your checks, using the exact same syntax you use in crontab files.
