# Runbooks

Source: https://docs.quake.ai/docs/operate/runbooks
Markdown: https://docs.quake.ai/docs/operate/runbooks.md

---

# Runbooks

A runbook is a step-by-step procedure for handling a specific operational scenario. Runbooks reduce mean time to resolution (MTTR) by giving you a tested, repeatable path from symptom to fix; no guesswork under pressure.

Each runbook in this section follows a consistent structure:

1. **Symptoms**: what you observe (error messages, metrics, user reports)
2. **Diagnosis**: how to confirm the root cause
3. **Resolution**: step-by-step fix with commands and expected output
4. **Verification**: how to confirm the issue is resolved
5. **Prevention**: changes to avoid recurrence

<DocsSectionLinks section="operate/runbooks" />

## Available runbooks

## Additional references

These existing guides cover supplementary operational procedures:

- [Interrupt VM boot process](/docs/operate/troubleshooting/interrupt-vm-boot): recover an instance stuck in a boot loop or locked out by a misconfiguration
- [Retrieve Windows password](/docs/operate/troubleshooting/retrieve-windows-password): recover access to a Windows Server instance
- [Advanced Kubernetes troubleshooting](/docs/operate/troubleshooting/advanced-kubernetes): diagnose control plane and workload issues
- [Create an instance snapshot](/docs/compute/how-to/create-snapshot): create a point-in-time backup before maintenance
- [Allocate floating IPs](/docs/network/how-to/allocate-floating-ips): restore public access after a networking change

## See also

- [Operate overview](/docs/operate)
- [Monitoring](/docs/operate/monitoring)
- [Troubleshooting](/docs/operate/troubleshooting)