From the course: Site Reliability Engineering: Service-Level Agreements and Objectives
Join today to access over 22,500 courses taught by industry experts or purchase this course individually.
Common measurements
From the course: Site Reliability Engineering: Service-Level Agreements and Objectives
Common measurements
- [Instructor] One common way to get started with service level indicators is to think about your system abstractly and segment it into pieces based on common component types. Typically, components of a system will fall into one of three categories; one, request-driven systems also referred to as user-facing serving systems; two, big data systems also referred to as data processing pipelines; and three, storage systems. We'll look at request-driven systems first. Request-driven systems are components where a user creates some type of event and expects a response back in return. This could be a RESTful service where the user interacts with a browser or an API used by a mobile application. In request-driven systems, it's generally important to think about the following types of service level indicators. Availability, could we respond to the request? Latency, how long did it take to respond? And throughput, how many requests…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.