Interview kitsBlog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2026 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Observability
Observabilityeasy

Explain the RED and USE methodologies and when to use them.

Tags
#red#use#metrics
Back to categoryPractice quiz

Answer

RED (Rate, Errors, Duration) is best for request-driven services. USE (Utilization, Saturation, Errors) is best for resources like CPUs, disks, or queues. Together they cover service health and resource bottlenecks.

Advanced answer

Deep dive

Pick the framework based on what you’re observing:

  • RED: APIs, web services, RPCs.
  • USE: infrastructure resources, queues, caches.
  • Combine with SLOs for user impact.

Examples

RED for HTTP:

Rate = requests/sec
Errors = % non-2xx
Duration = p95/p99 latency

USE for CPU:

Utilization = % CPU
Saturation = run queue length
Errors = throttling or faults

Common pitfalls

  • Using RED for non-request resources.
  • Ignoring saturation, which predicts future failure.
  • Focusing on averages instead of tail latency.

Interview follow-ups

  • How would you apply USE to a database?
  • What is the fastest signal for a user-facing outage?
  • How do RED/USE map to SLOs?

Related questions

Observability
What dashboards are must-have for a critical API?
#dashboards#red#slo
Observability
How do you handle high-cardinality labels/tags in metrics?
#metrics#cardinality#labels
Observability
Logs vs metrics vs traces — when do you use each?
#observability
#logs
#metrics
Testing
What does code coverage tell you and what does it not?
#coverage#quality#metrics