JobTick

Ruby

Rails job monitoring for Whenever, Solid Queue, and Sidekiq. Know when your scheduled jobs stop running — before your users do.

The problem

Your error monitor catches exceptions. Mission Control shows you failed jobs. Neither tells you when a recurring job simply stops running.

No exception. No alert. Nothing.

The Solid Queue scheduler process dies at 2am. Your nightly invoice job hasn't run in three days. Your users notice before you do.

JobTick solves this. It watches every scheduled job in your Rails app and alerts you the moment one goes silent — even when no error is raised.

Why JobTick over Healthchecks.io or Cronitor?

Those tools work — but they require you to manually add a heartbeat ping to every job. Touch 15 job files. Name each monitor by hand. Keep names in sync when jobs are renamed or removed.

JobTick reads your existing config files and registers everything automatically.

config/schedule.rb      → Whenever jobs, auto-discovered
config/recurring.yml    → Solid Queue recurring tasks, auto-discovered
sidekiq.yml             → Sidekiq periodic jobs, auto-discovered

Add the gem. Add your API key. Deploy. Done.

Installation

Add to your Gemfile:

gem 'jobtick'

Create an initializer:

# config/initializers/jobtick.rb
JobTick.configure do |config|
  config.api_key = ENV['JOBTICK_API_KEY']
end

That's it. On next deploy, JobTick reads your schedule config, registers a monitor for every job, and starts tracking.

No changes to individual job files. No manual monitor creation. No names to keep in sync.

What gets monitored

Solid Queue (config/recurring.yml)

# Your existing recurring.yml — no changes needed
nightly_report:
  class: NightlyReportJob
  schedule: every day at 3am

sync_exchange_rates:
  class: ExchangeRateJob
  schedule: every hour

At boot, JobTick reads this file and registers a monitor for each entry. It then installs an around_perform hook into ActiveJob::Base so every job execution automatically sends started, completed, and failed pings. No changes to your job files.

Sidekiq periodic jobs

Supports both sidekiq-cron and Sidekiq::Periodic:

# sidekiq-cron — loaded from config/sidekiq_cron.yml or in an initializer
Sidekiq::Cron::Job.create(name: 'Nightly Cleanup', cron: '0 2 * * *', class: 'NightlyCleanupWorker')

# Sidekiq::Periodic
Sidekiq.configure_server do |config|
  config.periodic do |mgr|
    mgr.register('0 * * * *', HourlyDigestWorker)
    mgr.register('0 2 * * *', NightlyCleanupWorker)
  end
end

JobTick installs a server middleware that wraps every job execution. For native Sidekiq workers (Sidekiq::Worker subclasses) pings are sent by the middleware. For Active Job workers dispatched through Sidekiq, pings are sent by the around_perform hook instead, so nothing is double-counted.

Whenever (config/schedule.rb)

Whenever schedules jobs as cron shell commands, so there is no Ruby hook point to instrument automatically. One setup step is required: run the generator and update your config/schedule.rb to use the jobtick_runner and jobtick_rake job types instead of the built-in runner and rake:

bundle exec rake jobtick:whenever:setup

This prints the two job_type definitions to add to the top of your schedule file, then use them in place of the standard types:

every 1.day, at: '2:00 am' do
  jobtick_runner 'InvoiceJob.perform_later', monitor_key: 'whenever.invoice_job'
end

every :hour do
  jobtick_rake 'reports:sync', monitor_key: 'whenever.reports_sync'
end

The job types wrap execution with curl pings to the JobTick API, so no changes to individual job classes are needed.

What you get

Silent failure detection — alerts when a job stops running entirely, not just when it raises an exception. The failure mode your error monitor misses.

Auto-sync on deploy — add a job to your schedule, it appears in your dashboard at next deploy. Remove a job, its monitor is automatically retired.

Run history — see every execution: start time, duration, exit status. Spot when a job starts getting slower before it becomes a problem.

Maintenance windows — deploying at 3am? Snooze any monitor for a set period so you don't get paged for expected downtime.

Team alerts — email and Slack notifications. On-call rotation support on higher plans.

Requirements

  • Ruby >= 3.3
  • Rails >= 7.0
  • One or more of: Whenever, Solid Queue, Sidekiq

Status

JobTick is currently in development. Sign up for early access at jobtick.app. Launching June 2026.

If you want to follow along or give early feedback, open an issue or watch the repo.

License

MIT. See LICENSE.

Built by Clearstack Labs