Technologies/Dramatiq/dramatiq.worker.idle
DramatiqDramatiqMetric

dramatiq.worker.idle

Workers currently idle
Dimensions:None
Available on:PrometheusPrometheus (1)OpenTelemetryOpenTelemetry (1)
Interface Metrics (2)
PrometheusPrometheus
Number of idle worker threads
Dimensions:None
OpenTelemetryOpenTelemetry
Number of workers currently idle and waiting for messages
Dimensions:None
Sources
dramatiq_worker_idle_threadsgithub.com
dramatiq.worker.idlegithub.com

Technical Annotations (16)

Configuration Parameters (3)
queue_namerecommended: high-priority, default, low-priority, bulk
Separate queues by priority to prevent head-of-line blocking
prefetch_multiplierrecommended: 1
prevents worker starvation in retry-heavy workloads
worker_timeoutrecommended: 100
Polling interval in milliseconds when queue is idle; lower values reduce task pickup latency (default is 1000)
Error Signatures (2)
Pushing message '.*' onto work queue.log pattern
Received message .* with id '.*'.log pattern
CLI Commands (3)
dramatiq config.dramatiq --threads 1 --processes 1 --log-file=dramatiq_log${VAR}.txtdiagnostic
dramatiq tasks --queues high-priority --threads 8remediation
dramatiq tasks --queues default low-priority --threads 4remediation
Technical References (8)
work queueconcepttime.sleepcomponentworker.pyfile pathmessage prefetchingconceptworker threadconceptWorkercomponentcli.pyfile pathworker_processcomponent
Related Insights (6)
Worker pool exhaustion from blocking retry delays prevents message processingcritical
▸
Missing 'Received message' log indicates worker pool exhaustionwarning
▸
Message prefetching causes worker starvation with concurrent taskswarning
▸
Worker thread pool exhaustion delays high-priority taskswarning
▸
Worker starvation under high retry load with default prefetch settingswarning
▸
High worker timeout causes task pickup latency when queue is idlewarning
▸