:large_orange_circle: LOW SEV · Enforcement Channe...
# alarms-prod
a
🟠 LOW SEV · Enforcement Channels Unsubscribed 🔥 Fewer than 4 enforcement pub/sub channels subscribed — cut/remove messages are being dropped <|📈 graph> · <|📊 service dashboard> · 🚨 alarm definition · 🔕 silence _ozone-api publishes to enforcement:cut, cut-all, remove and remove-cut-all. Redis pub/sub is fire-and-forget: a message published into a channel with no subscriber is discarded, not queued. WARNING RATHER THAN CRITICAL because it usually self-heals. For most activities inference emits a session-continued prediction every ~30s, which re-drives the enforcement decision, so a single dropped cut lands about a cadence late rather than never. A proxy restart legitimately dips the subscriber count for a few seconds. WHAT DOES NOT SELF-HEAL is a SUSTAINED gap — every re-drive lands in the same empty channel. That case escalates via 'Enforcement Channels Unsubscribed (sustained 30m)'. WE CANNOT SEE THE DROP RATE ITSELF. Redis exposes subscribers and channels, never deliveries: ozone-api records a successful PUBLISH and the proxy records nothing. This rule is a liveness proxy, not a delivery measurement. Baseline: 4 channels, 2 subscriber clients, dipped to 1 once in 7d. Panel: /d/redis-service-health 'Are enforcement decisions reaching the proxies?'. Ticket: CLE-514._ Grafana vmain-b1e6358