Sample runbook

High CPU on web tier

This is an example of what a Resolvify runbook looks like. AI generates these from your documentation, past incidents, and tribal knowledge—then refines them with success/failure feedback.

Runbook metadata

Trigger:: Alert: CPU > 80% for 5 min on web tier
Mode:: Approve-to-run (human signs off)
Risk level:: Medium (scaling action)

Step 1

Identify top CPU consumers

Run top -b -n 1 and correlate with process list. Check if spike correlates with recent deploy.

Step 2

Scale web tier (if load-driven)

If CPU is load-driven and below capacity limits, add 1–2 instances. Parameter: scale_count (default: 2).

Step 3

Restart runaway process (if identified)

If a single process is consuming > 70% CPU and is known-safe to restart, execute restart with 30s grace period.

Step 4

Log outcome and close ticket

Update ITSM ticket with action taken. If no resolution, escalate to L2 with context.

Rollback: Revert scale if CPU normalizes within 15 min; otherwise keep. Every execution is logged and auditable.

Want to see this in action with your stack?

Book a pilot