tag:blogger.com,1999:blog-8138074853469141757.post8181093456925060955..comments2024-03-24T02:21:19.242-07:00Comments on Building Technical Operations: The art of crontab jobs monitoring, part IIVictor Gartvichhttp://www.blogger.com/profile/04947678210909528976noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8138074853469141757.post-39947162701002333742014-04-19T20:09:12.107-07:002014-04-19T20:09:12.107-07:00This comment has been removed by the author.JamesWhitehttps://www.blogger.com/profile/06218388672253345917noreply@blogger.comtag:blogger.com,1999:blog-8138074853469141757.post-16850270200949272422012-06-28T11:15:38.212-07:002012-06-28T11:15:38.212-07:00Hi Victor. Thanks for the blog post. For the less ...Hi Victor. Thanks for the blog post. For the less technically inclined, or those who want something they can setup in a few minutes, I suggest they look at PushMon. PushMon will alert you of failed, delayed or missed jobs. All you need to do is create a PushMon URL and call this URL when your cron job successfully completes. Only requirement is internet connectivity so you can call the URL. Integration with Nagios passive checks can be implemented via the URL alert option.Bienvenido Davidhttps://www.blogger.com/profile/00384219366682391775noreply@blogger.com