The USE method is a troubleshooting approach created by Brendan Gregg. For each resource, such as CPU, memory, disks and network interfaces, you check Utilization (how busy it is), Saturation (how much work is waiting) and Errors (failed operations).
Why it matters
When a server is slow, it is tempting to guess. USE gives a short, systematic list so you rule resources in or out quickly. Saturation is the key addition: a CPU at 100% utilization with an empty run queue is fine, while a modest utilization with a long queue is a problem. It focuses on resources, so it pairs with the RED method, which starts from the user's requests.
Example
A quick pass on a Linux host:
CPU utilization: top / mpstat saturation: load average vs cores errors: dmesg
Memory utilization: free -m saturation: swap in/out (vmstat) errors: dmesg for OOM
Disk utilization: iostat -x saturation: await, queue length errors: smartctl
Network utilization: sar -n DEV saturation: drops, retransmits errors: ip -s linkWork through each row and note anything abnormal before changing configuration.
Common mistakes
- Looking only at utilization and ignoring queues.
- Forgetting software resources like connection pools, thread pools and file descriptors.
- Reading average values over long windows that hide short bursts.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.