Back to All Scenarios
PASSEDcloud / gcp_memorystore
GCP: Memorystore Redis OOM — Maxmemory Reached
GCP Memorystore for Redis reached its maxmemory limit. Write operations failing with OOM errors.
Pattern
UNKNOWN
Expected: GCP_REDIS_OOM
Severity
MEDIUM
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | GCP_REDIS_OOM | UNKNOWN | |
| Severity Assessment | HIGH | MEDIUM | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
GCP Memorystore for Redis M1 (5GB). Memory at 100%. maxmemory-policy: noeviction. All SET operations failing with OOM.
Injected Error Messages (1)
GCP Memorystore OOM — Redis instance at 5GB/5GB (100%), maxmemory-policy noeviction, all write operations failing with OOM, application caching broken
Neural Engine Root Cause Analysis
Unrecognized error pattern — this may be a new type of failure not yet cataloged.
Remediation Plan
Trigger autonomous healing to diagnose and fix. Manual investigation may be needed if healing cannot resolve.
Improvements Applied
- Pattern unrecognized — consider adding keywords for GCP_REDIS_OOM
- Severity: MEDIUM (expected HIGH)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr9bl09cclig7xvz9fn10