Dramatiq
v1.13.0 Apache-2.0z4j-dramatiq ยท Upstream project
Middleware-driven Dramatiq observability.
Ships as a single Z4JMiddleware with no monkey-patching. Supports Redis and RabbitMQ. Pending-task cancellation is promoted only with z4j-dramatiq[abort] and a real dramatiq-abort Abortable middleware; z4j never interrupts running Dramatiq work.
- Latest
- v1.13.0
- Released
- 2026-10-19
- License
- Apache-2.0
Install
pip install z4j-dramatiq Native actions
-
submit_task -
retry_task (complete replacement inputs) -
purge_queue -
cancel_task (pending only; requires [abort] and real Abortable middleware) -
list_dead_letters (Redis lists the entries; RabbitMQ reports the count only)
Marked entries are not in the adapter's default capability set. The adapter advertises them only when the stated condition holds (an installed extra and its middleware, or a supported broker), so the control does not appear otherwise.
Not supported
- running-task cancellation
- bulk_retry
- requeue_dead_letter
- restart_worker
- rate_limit
These are engine-level limitations: the underlying engine does not expose the primitives required to support these actions.
Wiring
How z4j plugs in
Event capture
Z4JMiddleware, Dramatiq's blessed observability hook.
Reconciliation
Reports unknown; the brain's event-derived snapshot remains authoritative.
Paired scheduler
APScheduler
Dashboard management for the APScheduler 3 jobstore.
z4j-apscheduler
Creates, edits, pauses and resumes native APScheduler jobs. Manual runs use its executor without moving the repeating schedule. Registered callables define the allowed task choices.
Learn moreMore engines