Technologies/Celery/celery.worker.tasks.active
CeleryCeleryMetric

celery.worker.tasks.active

Tasks currently executing
Dimensions:None
Available on:OpenTelemetryOpenTelemetry (1)Native (1)PrometheusPrometheus (1)
Interface Metrics (3)
OpenTelemetryOpenTelemetry
Number of tasks currently being executed by workers
Dimensions:None
Native
Number of currently active tasks being executed by worker
Dimensions:None
PrometheusPrometheus
Number of currently executing tasks by worker
Dimensions:None
Sources
celery.worker.tasks.activedocs.celeryq.dev
celery_worker_tasks_activegithub.com

Technical Annotations (10)

Configuration Parameters (4)
CELERYD_CONCURRENCYrecommended: 4
Controls the number of concurrent worker processes
max_tasks_per_childrecommended: 500
Worker restart interval to prevent memory leak accumulation
CELERYD_PREFETCH_MULTIPLIERrecommended: 1
limits concurrent unacked tasks per worker to prevent multiple stuck restoration attempts
CELERY_TASK_RESULT_EXPIRESrecommended: 600
task result expiration set to 10 minutes in affected configuration
Technical References (6)
OOMconceptunacked_mutexcomponentvisibility timeoutconceptkombu/transport/redis.py#L414file pathzrevrangebyscoreprotocolhgetprotocol
Related Insights (7)
Resource contention among workers wastes up to 30% of processing timewarning
▸
Insufficient worker processes cause task queue buildup and delayswarning
▸
Worker memory leaks cause restarts and task failurescritical
▸
Queue depth exceeding thresholds requires worker autoscalingwarning
▸
Scalability issues with high throughput task processingwarning
▸
Workers stuck processing large unacked tasks cause network congestion and worker stallscritical
▸
Unacked mutex expiration triggers cascading worker failures every 5 minutescritical
▸