DEV Community

Cover image for SLA & SLO & SLI
Ibrahim S
Ibrahim S

Posted on

SLA & SLO & SLI

đ—Ļ𝗟𝗔: đ—Ļ𝗲đ—ŋ𝘃đ—ļ𝗰𝗲 𝗟𝗲𝘃𝗲𝗹 𝗔𝗴đ—ŋ𝗲𝗲đ—ē𝗲đ—ģ𝘁𝘀

What is an SLA?

đŸ’ĸ An SLA (service level agreement) is an agreement between provider and client about measurable metrics like uptime, responsiveness, and responsibilities.

đ—Ļ𝗟đ—ĸ: đ—Ļ𝗲đ—ŋ𝘃đ—ļ𝗰𝗲 𝗟𝗲𝘃𝗲𝗹 đ—ĸđ—¯đ—ˇđ—˛đ—°đ˜đ—ļ𝘃𝗲𝘀

What is an SLO?

đŸ’ĸ An SLO (service level objective) is an agreement within an SLA about a specific metric like uptime or response time.

đŸ’ĸ So, if the SLA is the formal agreement between you and your customer, SLOs are the individual promises you are making to that customer.

đŸ’ĸ SLOs are what set customer expectations and tell IT and DevOps teams what goals they need to hit and measure themselves against.

đ—Ļ𝗟𝗜: đ—Ļ𝗲đ—ŋ𝘃đ—ļ𝗰𝗲 𝗟𝗲𝘃𝗲𝗹 𝗜đ—ģ𝗱đ—ļ𝗰𝗮𝘁đ—ŧđ—ŋ

What is an SLI?

đŸ’ĸ An SLI (service level indicator) measures compliance with an SLO (service level objective).

đŸ’ĸ So, for example, if your SLA specifies that your systems will be available 99.95% of the time, your SLO is likely 99.95% uptime and your SLI is the actual measurement of your uptime.

đŸ’ĸ Maybe it's 99.96%. Maybe 99.99%. To stay in compliance with your SLA, the SLI will need to meet or exceed the promises made in that document.

Top comments (0)