RED 与 USE 方法
学习两种经典的监控方法：面向请求驱动服务的 RED 和面向资源的 USE，并了解何时应用各自的方法来聚焦仪表板。
RED 与 USE 方法 是 CoddyKit 上的免费 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Why Methodologies?
With endless metrics available, teams drown in dashboards. RED and USE are proven recipes that tell you which few signals actually matter.
The RED Method
RED targets request-driven services and tracks three signals: Rate, Errors, and Duration.
- Rate: requests per second
- Errors: failed requests per second
- Duration: latency distribution
RED in Practice
For every service, chart these three. Together they answer how busy it is, whether it is failing, and whether it is slow.
rate(http_requests_total[5m])
rate(http_requests_total{status=~"5.."}[5m])
histogram_quantile(0.95, http_request_duration_seconds_bucket)Why RED Works
RED reflects what users feel: are their requests served, served correctly, and served quickly. It maps directly to user experience.
The USE Method
USE targets resources and tracks Utilization, Saturation, and Errors for each component like CPU, memory, disk, and network.
USE Defined
For each resource:
- Utilization: percent of time busy
- Saturation: queued work waiting
- Errors: error events
USE in Practice
Walk the resource list and apply USE to each, finding bottlenecks systematically rather than guessing.
CPU: utilization %, run-queue length, throttles
Disk: busy %, IO wait queue, IO errorsSaturation Is the Key
High utilization can be fine; saturation, the backlog of waiting work, is the early warning that a resource is becoming a bottleneck.
RED vs USE
They are complementary.
- RED: service health from the user view
- USE: resource health from the system view
RED tells you something is wrong; USE often tells you why.
Combining Both
A latency spike (RED Duration) might trace to disk saturation (USE). Using both methods links symptom to cause.
Building Focused Dashboards
Design service dashboards around RED and host dashboards around USE. This keeps panels meaningful instead of a wall of noise.
Quick Check
Match method to target.
Recap
You learned two focusing methodologies: RED (Rate, Errors, Duration) for request-driven services from the user perspective, and USE (Utilization, Saturation, Errors) for resources from the system perspective. RED reveals symptoms, USE reveals causes, and together they keep dashboards meaningful.
常见问题解答
「RED 与 USE 方法」课时是免费的吗？
是的 — 「RED 与 USE 方法」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课程的其余内容，请升级到 CoddyKit PRO。 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课程共包含 4 节课。
「RED 与 USE 方法」这节课中我会学到什么？
学习两种经典的监控方法：面向请求驱动服务的 RED 和面向资源的 USE，并了解何时应用各自的方法来聚焦仪表板。 你通过在浏览器中直接运行的动手代码来练习 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 需要有经验吗？
无需任何先前经验。CoddyKit 上的 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「RED 与 USE 方法」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课中编写并运行代码吗？
能。每节 System Observability: Logging, Metrics & Tracing (ELK + OpenTelemetry) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 关联日志、指标与追踪
- 异常检测与人工智能运维
- SLO、SLI 与错误预算
- RED 与 USE 方法