Back to All Scenarios
PASSEDcloud / azure_cosmos
Azure: Cosmos DB Request Units Exhausted
An Azure Cosmos DB container exceeded its provisioned RU/s. All writes being throttled with HTTP 429 responses.
Pattern
AZURE_CLOUD
Expected: AZURE_COSMOSDB_THROTTLE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AZURE_COSMOSDB_THROTTLE | AZURE_CLOUD | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Azure Cosmos DB container 'orders'. Provisioned: 1000 RU/s. Actual demand: 5000 RU/s during peak. Autoscale: not enabled. 80% of writes rejected.
Injected Error Messages (1)
Azure Cosmos DB throttled — container 'orders' at 1000 RU/s provisioned, demand 5000 RU/s, HTTP 429 TooManyRequests on 80% of writes, autoscale not enabled
Neural Engine Root Cause Analysis
Azure cloud infrastructure event detected — an Azure resource may be failing, an App Service is unhealthy, Azure AD authentication is disrupted, or a Service Bus queue is backed up. Azure outages can cascade across dependent services and affect both cloud-hosted applications and hybrid on-premises integrations relying on Azure AD.
Remediation Plan
1. Check Azure Service Health (status.azure.com) for any active incidents in your region.
2. Review Azure Monitor alerts and resource health for the affected service.
3. For App Service issues, check the Kudu console for application logs and restart the app if needed.
4. For Azure AD issues, verify conditional access policies and check the Azure AD sign-in logs for failure reasons.
5. For Service Bus, check dead-letter queues and verify the sending/receiving applications are connected and processing messages.
Improvements Applied
- Pattern classified as AZURE_CLOUD (expected AZURE_COSMOSDB_THROTTLE)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr8vc09c3lig7t04rmwnw