little-king-41579
03/11/2026, 12:43 PMtall-airline-16756
03/11/2026, 12:43 PMtall-airline-16756
03/11/2026, 12:43 PMload_threshold.
• If you still want to verify availability or monitor workers proactively, use the CLI status, run multiple workers for high availability, and monitor relevant metrics.
What LiveKit handles for you
• Workers register with the LiveKit server and report their load/health.
• The server performs load-based dispatching and will only send jobs to workers that are eligible (i.e., registered, connected, and under load_threshold).
• Explicit pre-checks are not required for correct dispatching because the server enforces availability when assigning jobs.
Ways to verify or monitor worker availability
• Use the CLI: run the agent status command to see health and current state of registered agents. This shows which workers are connected and their status.
• Run multiple workers per `agent_name`: this provides redundancy and automatic failover so dispatching is resilient if one worker becomes unavailable.
• Monitor metrics and telemetry:
◦ Track job queue depth and worker connectivity to detect bottlenecks or offline workers.
◦ Monitor worker load or CPU/memory for capacity planning (so workers don’t hit their load_threshold).
• Health checks & alerts:
◦ Configure liveness/readiness probes (or equivalent) for worker processes in your deployment platform so orchestration can restart unhealthy workers.
◦ Add alerts when worker count for an agent falls below a threshold.
If you want, I can:
• Show the exact agent status command output fields to look at.
• Suggest which metrics to collect (e.g., connected workers, queue length, worker load) and how to map them to alerts.
• Walk through a small script or API call to poll worker status periodically.
Which of these would you like next — CLI example, metrics/alert guidance, or a polling script?
Sources: Agents Framework | livekit/livekit_composite | DeepWiki | Agent dispatch | LiveKit Documentation