Slack log forwarder duplicate messages by replica count #7

Open
opened 2026-06-12 19:38:15 +00:00 by rasmus · 0 comments
Owner

Each replica listens for doorlog changes in database and forwards changes to Slack. This is IMO the most sensible way, vs duplicating each statement, and calling out to Slack in multiple codebases (leading to 'where exactly did this originate from / is broken at?).

Reduced replicas to 1 for time being. Locking via built-in kube primitives seems sensible (as the service already talks to kube api).

Each replica listens for doorlog changes in database and forwards changes to Slack. This is IMO the most sensible way, vs duplicating each statement, and calling out to Slack in multiple codebases (leading to 'where exactly did this originate from / is broken at?). Reduced replicas to 1 for time being. Locking via built-in kube primitives seems sensible (as the service already talks to kube api).
rasmus referenced this issue from a commit 2026-06-12 19:39:12 +00:00
Sign in to join this conversation.