Queue health summary
Combines pending counts, oldest-job age and active-worker coverage into a compact status for every supplied queue.
Day 023 / Frappe / Worker Queues
Worker Queue Reader
/ Overview
A read-only Python CLI that summarizes sanitized Frappe queue snapshots, worker coverage and stale backlogs without connecting to Redis.
A growing Frappe queue can mean ordinary backlog, a stale oldest job or no active worker coverage. Inspecting raw queue data can also expose job arguments and operational secrets.
/ Provided servicesClear thinking.
Clear thinking.
Practical delivery.
Privacy boundary
Reports only allowlisted operational facts and leaves job payloads, arguments and credentials outside the output.
Automation-ready behavior
Provides readable or JSON output with separate exit codes for clear state, attention required and invalid input.
/ Solution
Worker Queue Reader analyzes a supplied, sanitized JSON snapshot. It calculates queue depth, active-worker coverage and oldest-job age, then classifies each queue without connecting to Redis, executing Bench commands or mutating jobs.
/ Impact
Clear, backlog, stale and uncovered states
Timezone-aware oldest-job age
Only active workers count toward coverage
Arbitrary input fields omitted
Nine passing standard-library tests
Python standard library
Argparse, pathlib, JSON and timezone-aware datetime logic provide the full dependency-free CLI.
Frappe queue concepts
Models queue depth, worker subscriptions, active coverage and stale pending work from sanitized snapshots.
Unittest
Nine deterministic tests cover timestamps, queue states, worker status, totals, privacy, validation and CLI exits.