Back to All Scenarios
PASSEDcloud / azure_sql
Azure SQL DTU Limit Exhausted
An Azure SQL Database hit 100% DTU utilization. All queries slow or timing out. The service tier is too small for the current workload.
Pattern
HIGH_CPU
Expected: AZURE_SQL_THROTTLE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AZURE_SQL_THROTTLE | HIGH_CPU | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Azure SQL Database 'prod-db' on Standard S3 (100 DTU). DTU at 100% for 20 minutes. CPU: 98%. Log IO: 95%. 50+ queries waiting. Response times 30x normal.
Injected Error Messages (1)
Azure SQL DTU exhausted — database 'prod-db' at 100% DTU (Standard S3, 100 DTU), CPU 98%, Log IO 95%, 50+ queries waiting, avg response time 15 seconds (normal: 50ms)
Neural Engine Root Cause Analysis
High CPU utilization detected — the server's processor is at or near capacity, causing degraded application performance, increased response times, and potential service unavailability. Common causes include runaway processes, sudden traffic spikes, inefficient code paths, or crypto-mining malware.
Remediation Plan
1. Identify the top CPU-consuming processes using 'top' or 'htop' on the affected server.
2. Check for runaway or zombie processes and terminate them if safe to do so.
3. Review application logs for tight loops, excessive logging, or unoptimized queries.
4. Scale horizontally or vertically if the load is legitimate.
5. Check for unauthorized processes (crypto miners) if CPU usage is unexplained.
Improvements Applied
- Pattern classified as HIGH_CPU (expected AZURE_SQL_THROTTLE)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoopu001hlig7k2jh01h7