Technologies/RabbitMQ/celery.task.count
RabbitMQRabbitMQMetric

celery.task.count

Total tasks executed
Dimensions:None

Technical Annotations (15)

Configuration Parameters (5)
CELERY_BEAT_MAX_LOOP_INTERVALrecommended: 300
max sleep time between beat schedule iterations
CELERY_RESULT_BACKENDrecommended: None
result backend disabled in this deployment
prefetch_multiplierrecommended: 10
Increases throughput by 40% under heavy loads; use 1 for IO-bound tasks
worker_prefetch_multiplierrecommended: 1
configuration mentioned in deployment details, may affect task queueing behavior
broker_connection_retryrecommended: False
workaround to make worker crash on broker loss, requires restart policy
CLI Commands (3)
--prefetch-multiplier=1diagnostic
celery inspect pingdiagnostic
celery inspect active_queuesdiagnostic
Technical References (7)
celery beatcomponentperiodic tasksconceptprefetch multipliercomponentcatatonic stateconceptconsumer registrationconcepttransport levelconceptCeleryExecutorcomponent
Related Insights (5)
Low task volume deployment with periodic scheduled tasks on Kubernetesinfo
Prefetch multiplier tuning delivers 40% throughput gainwarning
Redis sustains 7000+ tasks/sec vs RabbitMQ 3500-4000info
Scalability issues with high throughput task processingwarning
Celery worker enters catatonic state after Redis broker restartcritical