Dramatiq
v1.10.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.10.0
- Released
- 2026-08-28
- License
- Apache-2.0
Install
pip install z4j-dramatiqNative actions
-
submit_task -
retry_task (complete replacement inputs) -
purge_queue -
cancel_task (pending only; requires [abort] and real Abortable middleware)
Marked entries are not in the adapter's default capability set. The adapter advertises them only when the named extra and its middleware are installed, 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.
How z4j plugs in
Event capture
Z4JMiddleware, Dramatiq's blessed observability hook.
Reconciliation
Reports unknown; the brain's event-derived snapshot remains authoritative.
APScheduler
Engine-agnostic scheduler. Pair with anything.
z4j-apscheduler
APScheduler is the best fit when you want one process to drive Dramatiq schedules (or any engine without a native scheduler).
Learn more
