The RED method is a streamlined approach for monitoring microservices and other request-driven applications, focusing on three critical metrics: Rate, Errors, and Duration. Originating from the principles established by Google's "Four Golden Signals," the RED monitoring framework offers a pragmatic and user-centric perspective on service performance.
The RED monitoring method is tailored to enhance end-user satisfaction, focusing on these 3 metrics:
Rate racks the number and, in certain contexts, the size of requests, such as photo uploads in a photo hosting service. Monitoring rate is crucial, especially in environments susceptible to peak traffic failures, noting that both spikes and drops in requests are significant.
Counts the number of failed requests per second. Error rates provide insights into the reliability and quality of the service. Errors represent any issues leading to incomplete or incorrect results, necessitating immediate resolution.
Records the time taken for each request. This aspect is crucial for assessing the service's responsiveness and efficiency. Duration metrics, capturing the time of requests, are vital for establishing the sequence of events, particularly in complex microservices environments. This aspect is crucial for both client-side and server-side interactions. In applications involving multiple services, pinpointing issues requires understanding...
Duration generally falls into the realm of distributed tracing, like OpenTracing and OpenTelemetry. Distributed tracing tracks the src and time your requests take between and within services, and brings events into causal order.
The RED method's effectiveness in its ability to track these aspects, aiding in identifying and resolving service or infrastructure-related problems. By giving us a solid, standardized starting point, RED makes it possible for separate teams to exchange clear information on concerns within the system, yet allows for expansion to cover unique needs and powers the drill down needed for cause analysis.
Learn more about RED monitoring in this presentation from .conf 2021.
So, what can RED do for you? Besides being an easy to remember acronym, RED tends to reduce decision fatigue in deciding how to get started observing your microservices applications. Its simplicity and clarity make the learning curve short. And it gives all of the teams, both operational and development, a common vocabulary to discuss issues and resolutions.
RED can be extended to build specifics for your unique needs based on your unique usage. And by tracking the src, duration and success of their requests, RED can serve as a proxy for user happiness.
Limitations
The RED Method represents a focused and effective strategy for monitoring microservices and other request-driven applications, ensuring that key performance indicators align with user experience and service reliability. Its simplicity and effectiveness make it a valuable tool for modern software architectures where user satisfaction is paramount.
See an error or have a suggestion? Please let us know by emailing ssg-blogs@splunk.com.
This posting does not necessarily represent Splunk's position, strategies or opinion.
The Splunk platform removes the barriers between data and action, empowering observability, IT and security teams to ensure their organizations are secure, resilient and innovative.
Founded in 2003, Splunk is a global company — with over 7,500 employees, Splunkers have received over 1,020 patents to date and availability in 21 regions around the world — and offers an open, extensible data platform that supports shared data across any environment so that all teams in an organization can get end-to-end visibility, with context, for every interaction and business process. Build a strong data foundation with Splunk.