Back to All Scenarios
PASSEDcloud / azure_redis
Azure: Azure Cache for Redis Memory Pressure — Evictions
Azure Cache for Redis is at 95% memory and actively evicting keys. Application cache hit rate collapsed.
Pattern
MEMORY_EXHAUSTION
Expected: AZURE_REDIS_PRESSURE
Severity
CRITICAL
Confidence
72%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AZURE_REDIS_PRESSURE | MEMORY_EXHAUSTION | |
| Severity Assessment | HIGH | CRITICAL | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Azure Cache for Redis C2 (2.5GB). Memory at 95%. allkeys-lru eviction active. 50,000 keys evicted in last hour. Cache hit rate: 20% (was 92%).
Injected Error Messages (1)
Azure Redis memory pressure — 95% memory used, allkeys-lru evicting 50K keys/hour, cache hit rate collapsed from 92% to 20%, downstream database overloaded
Neural Engine Root Cause Analysis
Memory exhaustion detected — the system has run out of available memory, triggering the OOM killer or forcing heavy swap usage. This causes severe performance degradation and can result in random process termination. Memory leaks in long-running applications are a common root cause, especially after deployments or configuration changes.
Remediation Plan
1. Check which process was OOM-killed using 'dmesg | grep -i oom' or journal logs.
2. Review memory usage by process with 'ps aux --sort=-%mem | head -20'.
3. Restart the affected service to reclaim leaked memory.
4. If a memory leak is suspected, enable heap profiling and analyze memory allocation patterns.
5. Consider increasing server memory or setting appropriate memory limits (cgroups/container limits).
Improvements Applied
- Pattern classified as MEMORY_EXHAUSTION (expected AZURE_REDIS_PRESSURE)
- Severity: CRITICAL (expected HIGH)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr9bk09c6lig7t0tcm3u1