Sidekiq retries are not enough when jobs go missing
Track actual completion signals and alert on missing or failed runs.
Retrying jobs can still break user workflows if processing never recovers or schedules are skipped.
- Retries hide outage duration
- No SLA signal for completion timeliness
- Critical jobs fail without team awareness
Step 1
Create one check per critical Sidekiq worker
Step 2
Send success ping after job completion
Step 3
Send fail ping on terminal error and alert channels
Ruby Sidekiq worker
class BillingSyncWorker
include Sidekiq::Worker
def perform
run_sync
Net::HTTP.post(URI('https://silentfail.dev/api/ping/YOUR_TOKEN/success'), '')
rescue StandardError
Net::HTTP.post(URI('https://silentfail.dev/api/ping/YOUR_TOKEN/fail'), '')
raise
end
endBuilt for developers. No credit card. Free for 1 check.
Lightweight ping API for cron, queue, and serverless runtimes.
Alerting channels: email + Slack, with event history for audits.
Public status available at /status.
Does this replace Sidekiq Web?
No, it adds proactive reliability alerts.
Can I monitor scheduled Sidekiq jobs?
Yes, set expected intervals per schedule.
Can I attach job IDs?
Yes, include context in message query parameters.
How fast can we set it up?
Usually in minutes with one ping endpoint.
Will this work with Rails?
Yes, Rails and pure Ruby workers are supported.