🔴 HIGH SEV · Redis AOF Write Failed
🔥 Redis AOF writes are failing on redis-prod-us-west-1 — a restart would now lose the keyspace
<|📈 graph> · <|📊 service dashboard> ·
🚨 alarm definition ·
🔕 silence
_AOF is the PRIMARY durability mechanism for Redis (appendonly yes, appendfsync everysec). While it is healthy a clean restart loses at most ~1s of writes. While it is broken, the next restart loses the mock-IP map (clients dial 198.18.x.x with no mapping) and every live proxy:block key (limits silently reset to unenforced) — and there is no replica to fall back on.
The cost is incurred now and collected later, so this must be fixed BEFORE any deploy or restart of Redis. Check disk space and permissions on /var/lib/redis first.
Baseline: pinned at 1 over 7d. Panel: /d/redis-service-health 'Would a restart lose the keys?'. Ticket: CLE-514._
Grafana vmain-b1e6358