How to monitor BullMQ jobs in Redis

1. 1. Connect to your Redis instance

   Add a Redis connection in RowDex — local Docker, staging ElastiCache, or production with TLS/SSH. Use read-only mode first if you are pointing at shared environments.

2. 2. Open the BullMQ panel

   RowDex auto-discovers BullMQ queues on the connection. You will see waiting, active, delayed, and failed counts without configuring a separate monitoring server.

3. 3. Inspect failed and stalled jobs

   Click into a queue to view job payloads, stack traces, and retry history. Failed jobs can be retried individually or in bulk — useful when a bad deploy poisoned a batch.

4. 4. Pause or resume workers safely

   Pause a queue while you fix schema or deploy code, then resume when ready. Combine with RowDex production warnings so destructive Redis commands require confirmation.

5. 5. Cross-check with your SQL database

   Because RowDex also connects to Postgres or MySQL in the same window, you can verify job side-effects — did the row actually update? — without leaving the app.

• Use separate connections for dev, staging, and prod — RowDex environment labels reduce wrong-window mistakes.
• Keep BullMQ monitoring on the same Redis DB index your workers use (usually 0, but verify in your app config).
• For high-volume queues, filter by failed state first; retry only after fixing the root cause.

Want the product overview? See the BullMQ monitor feature page or compare RowDex vs Redis Insight.