Queue monitoring
Monitor background jobs and queue status.
Overview
The Job queue tab shows the MongoDB-backed job queue that runs every monitor check. Use it to confirm jobs are firing and to spot jobs that keep failing.
Accessing the queue
- Navigate to Logs in the sidebar
- Click the Queue tab
Queue metrics
The metrics section displays overall queue statistics including active jobs, completed jobs and failed jobs.
Job table
The job table shows all monitoring jobs with:
- Monitor ID and URL: Which monitor the job belongs to
- Interval: How often the job runs (in milliseconds)
- Monitor type: HTTP, ping, port, etc.
- Run count: Total number of executions
- Fail count: Number of failed runs
- Last run: Timestamp of the most recent execution
- Status: Active, locked or failed indicator
Failed jobs
A separate table highlights jobs that have failed, showing the fail count, timestamp and failure reason. Investigate these to ensure all monitors are running correctly.
Queue actions
- Refresh: Reload queue data to see the latest status
- Flush queue: Stop the queue and start it again, which re-registers every job from the monitors that exist
Flushing does not delete monitors, checks or history. It is the thing to try when jobs appear stuck: locked jobs whose worker died are released, and the schedule is rebuilt from scratch. A check that was mid-flight when you flush is abandoned and runs again at its next interval, so the only cost is a possible gap of one interval.