Replace Hosted job monitoring
Queue depth, retries and failures for background work, watched from outside your application.
Why teams move off Hosted job monitoring
Watching your own queues from outside your own application, on a subscription.
What you give up
Little. This is among the easiest categories to bring in-house.
This directory says so when an engine only covers part of the job. A replacement that needs a caveat is still worth knowing about — it just should not surprise you in week three.
3 Rails engines that replace Hosted job monitoring
-
Mission Control — Jobs
Drop-in replacement OperationsQueue depth, failed jobs, retries and a retry button — for Solid Queue and other Active Job backends.
Hosted job monitoring → mission_control-jobs
No ratings yet → -
GoodJob
Drop-in replacement OperationsQueues, retries, scheduled jobs, cron and a dashboard — all in Postgres, all in your app.
Hosted job monitoring → good_job
No ratings yet → -
Sidekiq Web
Drop-in replacement OperationsQueues, retries, scheduled jobs and dead sets, in a Rack app you mount.
Hosted job monitoring → sidekiq
No ratings yet →
Questions
- Is there an open-source alternative to Hosted job monitoring for Rails?
- Yes — Mission Control — Jobs, GoodJob, and Sidekiq Web. They all mount into an application you already run, so there is no second deployment and no second database.
- What do I give up by replacing Hosted job monitoring?
- Little. This is among the easiest categories to bring in-house.
- How do I replace Hosted job monitoring in a Rails app?
- Add mission_control-jobs to your Gemfile, mount it in config/routes.rb at /jobs, and run its migrations. The whole integration is two lines and a migration.
- How much does replacing Hosted job monitoring save?
- Hosted job monitoring is priced varies. The engines here are open source, so the cost becomes the time to mount one and the resources it uses inside your existing application.
Same category
