Skip to content

Commit

Permalink
feat(tutorial): editing content
Browse files Browse the repository at this point in the history
  • Loading branch information
akristen committed Jun 21, 2023
1 parent 02bedd3 commit dfdab13
Showing 1 changed file with 14 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,26 @@ redirects:

import sonicSliUiOverview from 'images/sonic_screenshot-full_sli-ui-overview.webp'

## Objectives
Service levels measure the performance of different services within your system architecture. Tracking your service levels gives you greater oversight into the health of your system, allowing you to address poor performance before it becomes an issue to your customers.

By the end of this tutorial, you will:
By learning how to apply service levels to your app, you can improve and maintain your site's performance.

* Understand service level indicators (SLIs) and service level obectives (SLOs).
* Have created and defined SLIs and SLOs for your frontend experience.
* Have alerts set up to warn of any SLI or SLO breaches so you can react before they impact your users.
## Objectives [#objectives]

## Intro
This tutorial walks you through creating performance benchmarks with service levels. By the end of the tutorial, you'll have these tasks completed:

* Understand the relationship between service level indicators (SLIs) and service level obectives (SLOs).
* Create and defined SLIs and SLOs for your frontend experience.
* Set up alerts so you know when your services have a drop in performance.

## Title here [#]

Your system architecture is made up of hosts, apps, and services that affect and depend on each other. If one part of your architecture underperforms, it can create a cascading chain of events that could lead to critical system outages. Service levels, however, let you apply thresholds to these discrete parts. These thresholds apply a measurement to service behavior, so when performance exceeds or falls below that threshold, you're alerted. Here's how it works:

* A service level is made up of service level objectives (SLOs). SLOs are the goals that represent how you expect your services to behave.
* Your SLOs are defined by service level indicators (SLIs). SLIs are key measurements and metrics that determine service availability.
* On top of these objectives an indicators are alerts. These notify you when your services fail to meet your SLOs.

Let's look at the difference between service levels, SLOs and SLIs. Service levels describe services provided to users within a given period of time, in measurable terms. Service level objectives (SLOs) are the goals set for the availability expected out of a system. Service level indicators (SLIs) are the key measurements and metrics to determine the availability of a system.

Defining and managing your service levels following the steps below provides the ability to:

Expand Down

0 comments on commit dfdab13

Please sign in to comment.