SidekiqInsight provides detailed CPU, memory, and wall-time profiling for Sidekiq jobs and Rails requests, automatically detects memory leaks, stores metrics in Redis, and displays everything in a clean, modern dashboard. Ideal for monitoring production workload performance.

Moving your job to the Dead Job Queue INSTANTLY

Send Sidekiq status into Instrumental after every job

Keep track of fails in Sidekiq jobs

Manage your sidekiq jobs

Monitor currently running Sidekiq jobs to give user feedback

Signal a job to quit, and block the job from executing through middleware.

Syntax sugar for Sidekiq workers. Each consumer is a class, with clean interface, and custom logger. Usefull when count of different events ~100 and more.

Extends Sidekiq's web UI with useful features like reset buttons for processed/failed counters

Like the .delay method without YAML serialization.

SidekiqLiveness offers a solution to add liveness probe of a Sidekiq instance.

SidekiqLiviness offers a solution to add liveness probe of a Sidekiq instance.

Sidekiq includes a jobs dependencies mechanism to prevent a job from running before another one when enqueued. But sometime your jobs will be enqueued independently, then for you do not know the job id on which you depend on (you could parse Sidekiq queue, but...) `SidekiqLockableJob` allows yo...

Module for Rails mailers that sends the mail in the background. Adapted from the resque_mailer gem.

Marshal encoder for sidekiq. Enables when required.

This gem provides the ability to configure the maximum number of jobs a Sidekiq worker will process before terminating. For an environment running Kubernetes this is a perfect addition because once the affected pod dies it will automatically be restarted [gracefully] resetting memory, database-co...

A Sidekiq plugin that provides an MCP (Model Context Protocol) server for LLMs to interact with Sidekiq queues, stats, and failed jobs

Restart Sidekiq gracefully when exceeding preset memory limit

A small in-process watchdog that quiets Sidekiq with TSTP, waits for busy jobs to drain, and exits for a clean restart when RSS exceeds a configured limit.

Some exceptions are transient, so notifying an admin is not useful.