Live
#1 high infra_monitor
Infra Monitor: CPU usage critically high at 94.2%, rapidly escalating.
Host: claw-gateway1 CPU usage has reached 94.2% and is trending sharply upward (+61.5% over last 5 readings), crossing the critical red threshold of 95%. All other metrics are healthy with memory at 42.7%, disk usage well under capacity, and process count nominal at 140. Immediate investigation required to identify the resource-consuming process or workload. CPU: 94.2% | Memory: 42.7% Anomalies: CPU usage 94.2% — critically high and approaching absolute maximum, CPU trending upward at +61.5% over last 5 readings — unsustainable trajectory
Opened 2026-07-24 00:03 UTC · Resolved 2026-07-24 00:20 UTC
Handoff Notes ← Dashboard
Timeline
⬡
WEBHOOK
2026-07-24 00:03 UTC
Alert received from AI Infra Monitor. Host: claw-gateway1, Severity: HIGH
◎
CONTEXT AGGREGATED
2026-07-24 00:03 UTC
Sources available: 3/3 — Runbook: ✓ | Past incidents: ✓ | Infra health: ✓
✦
Response Plan
2026-07-24 00:03 UTC

Severity

P1 — claw-gateway1 CPU at 94.2%, trending +61.5%, will breach 95% ceiling within minutes; risk of service degradation/outage.

Root Cause

  • Runaway process consuming CPU (identify via top/ps aux)
  • Deployment or workload spike triggering resource exhaustion

Actions

  1. SSH to claw-gateway1 and run top -bn1 | head -20 + ps aux --sort=-%cpu | head -15 to identify culprit process.
  2. Cross-check Incident Logger for pattern: spike vs. sustained; assess if recent deploy correlates.
  3. Kill or throttle offending process if safe; else prepare for controlled restart.
  4. Confirm CPU drops below 85% and stabilizes.
  5. Document process name and CPU% spike in ticket for post-incident review.

Watch

  • CPU % — must drop to <80% within 5 min; if still >90%, escalate immediately.
  • Process count — watch for new processes spawning; indicates cascading failure.

Escalate If

CPU remains >95% after process termination OR unable to identify culprit within 3 minutes.

△
STATUS CHANGE
2026-07-24 00:15 UTC
Auto-resolver: CPU at 13.5% (below 70% clear threshold) — clean check 1/2
△
STATUS CHANGE
2026-07-24 00:15 UTC
Auto-resolver: CPU at 13.5% (below 70% clear threshold) — clean check 1/2
△
STATUS CHANGE
2026-07-24 00:20 UTC
Auto-resolver: CPU at 13.5% (below 70% clear threshold) — clean check 2/2
△
STATUS CHANGE
2026-07-24 00:20 UTC
AUTO-RESOLVED: CPU sustained below 70% for 2 consecutive checks. Current value: 13.5%
·
HANDOFF
2026-07-25 00:08 UTC
Handoff notes generated: # Shift Handoff Notes - **Incident:** CPU spike on claw-gateway1 reached 94.2% at 00:03 UTC on 2026-07-24 with rapid escalation (+61.5% trend). P1 severity due to risk of service degradation. - **Resolution:** Auto-resolver detected CPU sustained below 70% threshold for 2 consecutive checks; incident auto-resolved at 00:20 UTC with CPU at 13.5%. Root cause (runaway process or workload spike) was not explicitly identified in logs. - **Current State:** claw-gateway1 operating normally. No manual intervention was required. - **Watch For:** Monitor claw-gateway1 CPU closely over next shift for recurrence. If spike returns, manually SSH in and run `top -bn1 | head -20` + `ps aux --sort=-%cpu | head -15` to identify the culprit process. Check Incident Logger for deployment correlation and workload patterns. - **Outstanding Items:** Determine if spike was tied to recent deployment or workload change; consider adding process-level alerts if this becomes a pattern.
Update Status
Context Sources
RAG Runbook fetched ↗
Incident Logger fetched ↗
Infra Monitor fetched ↗
Details
ID #1
Severity HIGH
Source infra_monitor
Status RESOLVED
Opened 2026-07-24 00:03