celery-monitor

Inspect Redis broker data to diagnose Celery task queue health.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/michaelayoade/dotmac_crm --skill celery-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: celery-monitor
Source: https://github.com/michaelayoade/dotmac_crm/tree/main/.claude/skills/celery-monitor
Command: npx skills add https://github.com/michaelayoade/dotmac_crm --skill celery-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Celery systems often fail silently or slow down due to backlogs, dead workers, or stuck/failed tasks, and it can be difficult to pinpoint the root cause quickly.

Core Features & Use Cases

  • Queue depth inspection: Detect pending task backlog by checking the Redis list backing the default queue.
  • Worker liveness checks: Confirm whether workers are alive by looking for heartbeat key patterns.
  • Failure and stuck-task triage: Identify failed tasks via task-meta states and surface long-running STARTED tasks that may be stuck, then correlate with container logs when needed.
  • Result backend hygiene: Estimate whether task result entries are accumulating by counting task-meta keys and understanding expiry behavior.

Quick Start

Use the celery-monitor skill to inspect queue depth, worker heartbeats, and failed or stuck tasks in Redis MCP for your Celery deployment.

Frequently Asked Questions about celery-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a Celery queue backlog when tasks are pending?

Diagnosing a Celery queue backlog involves inspecting the Redis list backing the default queue to detect pending tasks. Analyzing these Redis data structures reveals queue depth and helps pinpoint the root cause of task processing delays.

How can I check Celery worker health using Redis?

Checking Celery worker health with Redis involves querying for heartbeat key patterns to confirm liveness. Locating these heartbeat keys verifies that workers are actively running and processing tasks within the deployment.

What is the best way to identify failed or stuck Celery tasks?

Identifying failed or stuck Celery tasks requires inspecting task-meta JSON state fields in the Redis result backend. Examining status, date_done, and traceback fields surfaces failed tasks and detects long-running STARTED tasks that may be stuck.

Does this approach to Celery monitoring require querying Redis directly?

Yes, this approach to Celery monitoring requires querying Redis directly. It inspects Redis broker and result-backend data structures, interpreting list, set, and string patterns to evaluate queue health, worker liveness, and task states.

Why are Celery task results accumulating in Redis?

Celery task results accumulate in Redis when task-meta entries are not expiring properly. Counting task-meta keys and understanding expiry behavior estimates result backend hygiene and determines whether results are accumulating unnecessarily.