Healthchecks.io is a monitoring service for your cron jobs. Have you ever thought "If this nightly backup script breaks one day, six months from now, I wonder how soon will anyone notice?". With Healthchecks monitoring, you will get notified just minutes after your cron job fails to complete on time. With PagerDuty integration, Healthchecks will be able to use PagerDuty alerting functionality already implemented in your organization.
Setting up the monitoring for your cron jobs only takes minutes. For each monitored cron job, Healthchecks.io creates a unique ping URL. Edit each cron job to send a HTTP request to its ping URL just before the job finishes. Healthchecks.io keeps track of the received pings, and sends alerts as soon as any of your cron jobs does not check in at the expected time.
Categories |
|
---|---|
Website | github.com |
Pricing URL | - |
Details $ | - |
Release Date | - |
Categories |
|
---|---|
Website | healthchecks.io |
Pricing URL | Official Healthchecks.io Pricing |
Details $ | freemium $20.0 / Monthly (100 checks, 10 team members) |
Release Date | 2015-07-01 |
No features have been listed yet.
Based on our record, Healthchecks.io seems to be a lot more popular than Resque. While we know about 153 links to Healthchecks.io, we've tracked only 5 mentions of Resque. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
You can use a background job queue like Resque to scrape and process data in the background, and a scheduler like resque-scheduler to schedule jobs to run your scraper periodically. Source: almost 2 years ago
So how do we trigger such a long-running process from a Rails request? The first option that comes to mind is a background job run by some of the queuing back-ends such as Sidekiq, Resque or DelayedJob, possibly governed by ActiveJob. While this would surely work, the problem with all these solutions is that they usually have a limited number of workers available on the server and we didn’t want to potentially... - Source: dev.to / about 2 years ago
Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck. - Source: dev.to / about 2 years ago
The Schedules worker corresponds to the appwrite-schedule service in the docker-compose file. The Schedules worker uses a Resque Scheduler under the hood and handles the scheduling of CRON jobs across Appwrite. This includes CRON jobs from the Tasks API, Webhooks API, and the functions API. - Source: dev.to / almost 3 years ago
There are a few of popular systems. A few need a database, such as Delayed::Job, while others prefer Redis, such as Resque and Sidekiq. - Source: dev.to / about 3 years ago
In fact, your platform (https://healthchecks.io/) is a prime example of where running customer wasm would be really excellent. Instead of sending webhooks out to customer configured URLs, you could run a Wasm environment to execute customer code. Off hand, a good use case here is to do further inspection of the event before it gets sent off to some other system - maybe there are cases where you send... - Source: Hacker News / about 2 months ago
Healthchecks.io — Monitor your cron jobs and background tasks. Free for up to 20 checks. - Source: dev.to / 2 months ago
I use healthchecks.io and have been very happy. Source: 4 months ago
With Uptime Kuma and healthchecks.io, you can do everything. Uptime Kuma to monitor "services" (web server, database), and healthchecks to monitor punctual jobs (backup jobs, etc). Source: 4 months ago
Is there anything different from https://healthchecks.io/ --- a service I've been using for free for a couple years now? - Source: Hacker News / 7 months ago
Sidekiq - Sidekiq is a simple, efficient framework for background job processing in Ruby
Cronitor - Monitor cron jobs, micro-services, daemons and almost anything else, no setup required. Easier cron troubleshooting and no more silent failures.
Hangfire - An easy way to perform background processing in .NET and .NET Core applications.
Cronhub - Cronhub helps you to easily monitor all your cron jobs in a beautiful dashboard. It alerts you when your cron job doesn't run on time or it fails.
delayed_job - Database based asynchronous priority queue system -- Extracted from Shopify - collectiveidea/delayed_job
Dead Man's Snitch - Monitor Cron Jobs and Windows Scheduled Tasks with ease.