Technologies/Celery/celery.task.received
CeleryCeleryMetric

celery.task.received

Tasks received by workers
Dimensions:None
Available on:Native (1)PrometheusPrometheus (1)DatadogDatadog (1)
Interface Metrics (3)
Native
Number of tasks received by workers
Dimensions:None
PrometheusPrometheus
Total number of tasks received by workers
Dimensions:None
DatadogDatadog
Number of tasks received by workers
Dimensions:None
Sources
task-receiveddocs.celeryq.dev
celery_task_received_totalgithub.com
celery.task.receivedgithub.com

Technical Annotations (17)

Configuration Parameters (1)
CELERY_BROKER_URLrecommended: redis://svc--redis.namespace:6379/3
broker connection used for worker communication
Error Signatures (6)
Connection to broker lost. Trying to re-establish the connectionlog pattern
ConnectionResetError: [Errno 104] Connection reset by peerexception
redis.exceptions.ConnectionError: Error while reading fromexception
missed heartbeat from celery@log pattern
No nodes replied within time constrainterror code
Error: No nodes replied within time constraintlog pattern
CLI Commands (3)
celery -b $CELERY_BROKER_URL inspect ping -d celery@$HOSTNAMEdiagnostic
celery -A saleor inspect statsdiagnostic
celery -A proj reportdiagnostic
Technical References (7)
kombu.transport.rediscomponentcelery.worker.consumer.consumercomponentrestore_visiblecomponentMutexcomponentliveness probeconceptreadiness checkconceptevent loopcomponent
Related Insights (2)
Celery worker stops consuming tasks after Redis connection reset and fails to recover automaticallycritical
▸
Celery worker stops responding to inspect commands after 1-3 days of runtimecritical
▸