solid_queue_guard

Your Solid Queue production doctor.
Catch dead workers, queue lag, and broken config before the 3am page.

Quick start · What it checks · Checks · Configuration · Mission Control · Changelog

Rails 8 ships with Solid Queue. Redis is optional. Production config is not.

Your web tier can be green while your jobs are dead. solid_queue_guard catches that before it becomes an incident.

Mission Control shows what is happening. solid_queue_guard warns what is dangerous.

bundle add solid_queue_guard
bin/rails solid_queue_guard:install
bin/rails solid_queue_guard:doctor

# config/routes.rb
mount SolidQueueGuard::Engine, at: "/solid_queue_guard"

curl localhost:3000/solid_queue_guard/health
SOLID_QUEUE_GUARD_STRICT=1 bin/rails solid_queue_guard:doctor   # CI gate
bin/rails solid_queue_guard:report                              # config + runtime

Full options: docs/configuration.md

CLI extras: SOLID_QUEUE_GUARD_FORMAT=json, SOLID_QUEUE_GUARD_SCOPE=config|runtime|all.

SolidQueueGuard Report

Status: DEGRADED

Checks:
✅ Active Job adapter is :solid_queue
❌ Worker threads: 10, queue DB pool: 5
⚠️ No workers configured for "mailers" queue

Suggested fixes:
- Increase queue DB pool to at least 12 or reduce worker threads

One command. Actionable output. No Datadog required to get started.

Config (pre-deploy / CI): adapter, queue DB, schema, thread vs pool sizing, worker coverage, scheduler/recurring.yml, env flags, Puma co-location, topology recommendations.

Runtime (production health): queue lag, stale processes, missing roles (supervisor/worker/dispatcher/scheduler), failed jobs, recurring staleness, blocked/orphaned claims, paused-queue lag, pidfile, finished-jobs growth.

Full ID list and thresholds: docs/checks.md

Opt-in Guard tab for Mission Control — Jobs:

gem "mission_control-jobs"

SolidQueueGuard.configure { |config| config.integrate_mission_control = true }

mount MissionControl::Jobs::Engine, at: "/jobs"
mount SolidQueueGuard::Engine, at: "/solid_queue_guard"

Requires mission_control-jobs and an asset pipeline (Propshaft or Sprockets). Load balancers should keep using /solid_queue_guard/health.

Opt-in continuous depth gauges (same DB source as Mission Control) plus Active Job event counters:

bundle add dogstatsd-ruby
bin/rails generate solid_queue_guard:metrics

Emits solid_queue.ready.count, solid_queue.ready.oldest_age_seconds, failed/claimed/scheduled counts, and solid_queue.jobs.* — see docs/configuration.md.

On non-healthy CLI runs you can notify via Rails logger, Slack, Datadog events, or a generic webhook (config.notify_with). Guard health status can also export to StatsD, Prometheus, or OpenTelemetry (config.metrics_backends).

Stable until 2.0 — semantic versioning:

Internal check classes and registry are @api private.

Use both.

• solid_queue >= 1.0, < 2.0
• mission_control-jobs — optional
• dogstatsd-ruby — optional (operational metrics)

See CHANGELOG.md for release notes.

See CONTRIBUTING.md for setup, bin/console, Appraisal matrix, and script/validate_revelo.sh.

bundle exec rake test
bundle exec rubocop
bundle exec appraisal rake test
gem build solid_queue_guard.gemspec

MIT — see MIT-LICENSE.

Run the doctor before you run the deploy.
_{Built for Rails teams who chose Solid Queue and still sleep at night.}