🔴 HIGH SEV · Redis Connections Rejected (block checks failing open)
🔥 Redis is rejecting connections — enforcement is failing open, silently and uncountably
<|📈 graph> · <|📊 service dashboard> ·
🚨 alarm definition ·
🔕 silence
_A rejected connection is not a retry-and-recover for ozone-proxy: it is a block check that cannot happen. enforcement.go discards the Redis error at all three decision points (cut-all :76, ResolveDomainActivities :49, IsActivityBlocked :60), so the connection is ALLOWED and nothing records that it should not have been. Children browse past their limits and no counter moves.
Usually the maxclients ceiling (default 10,000) or a client-side connection leak — check 'Can clients still connect?' for the trend, and which service grew.
Baseline: 0 lifetime; 79 clients, 102 max over 7d. Panel: /d/redis-service-health. Ticket: CLE-514 (section 0 covers the missing fail-open counter)._
Grafana vmain-b1e6358