Back to All Scenarios
PASSEDcloud / gcp_pubsub
GCP: Pub/Sub Subscription Backlog — Consumer Offline
A GCP Pub/Sub subscription has a growing message backlog because all subscriber instances were terminated during a GKE node upgrade.
Pattern
UNKNOWN
Expected: GCP_PUBSUB_BACKLOG
Severity
MEDIUM
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | GCP_PUBSUB_BACKLOG | UNKNOWN | |
| Severity Assessment | HIGH | MEDIUM | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
GCP Pub/Sub topic 'events'. Subscription 'events-processor'. All 4 subscriber pods terminated during GKE upgrade. Backlog: 2M messages. Oldest: 6 hours.
Injected Error Messages (1)
GCP Pub/Sub backlog — subscription 'events-processor' has 2M unacked messages, all subscriber pods terminated during GKE node upgrade, backlog age: 6 hours, growing 5K msg/min
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_PUBSUB_BACKLOG
- Severity: MEDIUM (expected HIGH)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr9bl09c9lig7gorqkddc