Technologies/Redis/celery.worker.heartbeat
RedisRedisMetric

celery.worker.heartbeat

Worker heartbeat events
Dimensions:None

Technical Annotations (22)

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 (5)
celery -b $CELERY_BROKER_URL inspect ping -d celery@$HOSTNAMEdiagnostic
celery -A saleor inspect statsdiagnostic
celery -A proj reportdiagnostic
celery -A your_app inspect pingdiagnostic
celery worker --without-heartbeat --without-gossip --without-mingleremediation
Technical References (10)
kombu.transport.rediscomponentcelery.worker.consumer.consumercomponentrestore_visiblecomponentMutexcomponentliveness probeconceptreadiness checkconceptevent loopcomponentheartbeatconceptgossipconceptmingleconcept
Related Insights (5)
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
Worker heartbeat failures correlate with 25% reduction in downtime when alertedcritical
Worker heartbeat latency indicates network or broker issueswarning
Celery worker flags prevent catatonic state but disable cluster featureswarning