Laravel Queue Dashboard

Real-time job processing across replicas and processes

Default connection: sqs · Queue: default

Live · Updated 07:38:28

Queue Actions

Cluster tests use the same connection/queue as your Queue Cluster. OOM: backlog + large-memory jobs. Stuck at 1: sustained backlog.

0
Pending in Queue
0
Active Replicas
0
Active Processes
0
Processed/min

Running jobs by replica

0 in queue

Each box is a worker that reported running jobs (replica ID from hostname). “Laravel Cloud API” is the environment replica count from Cloud; the number of boxes is how many workers reported jobs. Replica & process come from the worker when reported; otherwise they appear under “Processing (no assignment)”. Pending jobs stay in the queue until a worker picks them up.

¯\_(ツ)_/¯
No jobs running
Queue is empty. Start a test above to see activity.
Start a test above to see activity

Recent Job Activity

[17:06:01] ✗ 2 —:— sleep:file_upload
[17:06:06] ✗ 6 —:— memory:data_analysis
[17:06:06] ✗ 5 —:— memory:data_analysis
[17:06:07] ✗ 7 —:— cpu:video_encoding
[17:06:07] ✗ 4 —:— memory:data_analysis
[17:06:07] ✗ 3 —:— memory:data_analysis
[17:06:07] ✗ 1 —:— cpu:video_encoding
[17:06:08] ✗ 8 —:— cpu:data_encryption

System Info

Data source: sqs
Queue: default
Replicas: Simulated Set LARAVEL_CLOUD_API_TOKEN and LARAVEL_CLOUD_ENVIRONMENT_ID for replica count from Laravel Cloud.
Pending (total): 0
Failed jobs: 8
SQS available: 0
SQS in flight: 0
SQS delayed: 0
Recent job entries: 8

Job Type Legend

CPU Jobs (Video, ML, Encryption)
Memory Jobs (Images, Data, Reports)
Sleep Jobs (APIs, Uploads, Webhooks)
Small (cluster test)
Large memory (cluster test)