The RED Method: what do you monitor in your services
Submitted by Goutham V (@putadent) on Monday, 15 January 2018
Technical level: Intermediate Status: Submitted
The RED Method defines three key metrics you should measure for every microservice in your architecture; inspired by the USE Method from Brendan Gregg, it gives developers a template for instrumenting their services and building dashboards in a consistent, repeatable fashion.
In this talk we will discuss patterns of application instrumentation, where and when they are applicable, and how they can be implemented with Prometheus. We’ll cover Google’s Four Golden Signals, the RED Method, the USE Method, and Dye Testing. We’ll also discuss why consistency is an important approach for reducing cognitive load. Finally we’ll talk about the limitations of these approaches and what can be done to overcome them.
- Introduction: Why does it matter?
- RED Method
- How (Prometheus Implementation)
- Queries for the most frequent questions
- USE Method
- Four Golden Signals
Goutham is a student and a developer from India. His enthusiasm for Ops got him an internship on the infra team of a large company where he worked on Production infrastructure and built the company’s monitoring system on top of Prometheus.
That was his first encounter with production systems and Prometheus, and this summer, he started contributing to Prometheus and interned with CoreOS, working on Prometheus’ new storage engine. He is now a maintainer for Prometheus with a focus on TSDB, the storage engine powering it.