Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
From
medium
Site Reliability Engineering (SRE) is very popular lately, including the “Golden Signals” that you should be monitoring, but HOW do you actually get these data? This is a guide. 
No comment yet.
Sign up to comment
Scoop.it!
Golden signals are increasingly popular these days due to the rise of SRE. This article outlines what golden signals are, and how to monitor and use them in the context of various common services.
Mickael Ruau's insight:
There is no definitive agreement, but these are the three main lists of golden signals today:
You can see the overlap. USE is about resources with an internal view, while RED is about requests and real work, with an external view. In this article we will be focusing on a superset consisting of five signals:
Saturation & utilization are often the hardest to get, but they are also often the most valuable for hunting down current and future problems.
|
Scoop.it!
Tom Wilkie shares Weaveworks monitoring philosophy and the three most important metrics to use in your microservices architecture.
Mickael Ruau's insight:
Where does The RED Method come from? I can’t take any credit for this philosophy, as it is 100% based on what I learned as a Google SRE. Google calls it their “The Four Golden Signals”. The Google SRE book is a great read, and goes into way more depth that I can. Google include an extra metric, Saturation, over and above the RED method. I don’t include Saturation because, in my opinion, it is a more advanced use case. I think the first three metrics are really the most important, and people remember things in threes… But it you’ve mastered the first three, by all means include Saturation. The name “The RED Method” started life as a tongue-in-cheek play on Brendan Gregg’s USE Method - another recommended read. The USE Method was being circulated around the office when we started Weave Cloud and were discussing how to monitor it. I felt like I needed a catchy name for the monitoring strategy I was proposing, so The RED Method was born. The USE Method is a fantastic way to think about how to monitor resources; we use it as a framework to monitoring the infrastructure behind Weave Cloud. However, I think the abstraction becomes a little strained when talking about services.
Scoop.it!
Monitoring microservices effectively still can be a challenge, as many of the traditional performance monitoring techniques are ill-suited for providing the required granularity of system performance. Now a former Google and Weave engineer has developed an approach, called the RED Method, that seems to be gaining favor with administrators. RED “encourages you to come to …
|
There are three common lists or methodologies:
You can see the overlap, and as Baron Schwartz notes in his Monitoring & Observability with USE and RED blog, each method varies in focus. He suggests USE is about resources with an internal view, while RED is about requests, real work, and thus an external view (from the service consumer’s point of view). They are obviously related, and also complementary, as every service consumes resources to do work.
For our purposes, we’ll focus on a simple superset of five signals: