What is the difference between the USE method and the RED method? [Basic]
Answer
The USE method focuses on resources: utilization, saturation, and errors. The RED method focuses on request-driven services: rate, errors, and duration. USE is best for infrastructure components; RED is best for user-facing or request-serving services.
Technical explanation
USE asks whether a resource is busy, overloaded, or failing. It fits nodes, disks, NICs, JVM pools, database connections, and queues.
RED asks how much work is coming in, how many requests fail, and how long they take. It fits APIs, microservices, and RPC dependencies.
Both methods complement each other: RED detects user symptoms, while USE helps explain underlying resource causes.
Hands-on example
Example: if checkout p95 latency rises, RED tells you the service symptom. Then USE on the pods shows CPU throttling and queue saturation. The fix may be to raise CPU requests/limits, optimize code, or scale replicas.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Observability interview questions
- What is observability, and how is it different from traditional monitoring? [Basic]
- What are the three pillars of observability (metrics, logs, traces)? [Basic]
- What is the difference between monitoring and observability in practice? [Basic]
- What are the four golden signals of monitoring? [Basic]
- When would you use the USE method versus the RED method? [Basic]
- What is an SLI, an SLO, and an SLA, and how do they relate? [Basic]
- How do you choose good SLIs for a service? [Basic]
- How do you set an SLO target, and why not just aim for 100%? [Basic]