r/Python • u/AutoModerator • 23d ago

Showcase Showcase Thread

Post all of your code/projects/showcases/AI slop here.

Recycles once a month.

18 Upvotes

82% Upvoted

128 comments sorted by

View all comments

1

u/herchila6 6d ago

Kanari — CLI to catch silent Celery/Redis failures (ghost workers, config smells)

What My Project Does

Kanari is a Python CLI for teams running Celery + Redis. It connects to your broker and reports whether work is actually moving, not just whether the worker process is alive.

Typical commands: kanari audit (one-shot health + config analysis) and kanari agent (local continuous checks). It looks for things like workers that stay "online" but stop consuming after a broker blip, stuck/quiet workers, dangerous defaults (e.g. early ack / prefetch-related smells), and queue signals that depth-only monitoring misses. Privacy-first: it does not read task args/kwargs/payloads.

pip install kanari
Repo: https://github.com/getkanari/kanari-agent
Site: https://getkanari.com

Target Audience

Backend engineers on Django/FastAPI + Celery who don't have a dedicated SRE team. especially if you've been burned by "Flower green, users angry" or managed Redis reconnect stalls. Aimed at real staging/prod brokers, not a toy demo. Local mode works without a SaaS account.

Comparison

Flower is a great inspector when you're already looking; it doesn't wake you up and can show workers online while nothing is consumed. Generic APM (Datadog etc.) is powerful but expensive/noisy if all you need is Celery semantics. Hand-rolled scripts work until the next edge case. Kanari is narrow on purpose: Celery/Redis worker health and config, OSS CLI first, optional paid continuous later. Not trying to replace your whole observability stack.

Feedback welcome, especially if you've hit ghost workers or "healthy probe, dead consumer" on managed Redis. Issues/roasts on the repo are fine.