update SLO checklist page (#22690)

* initial updates * remove pdf * Update content/en/service_management/service_level_objectives/guide/slo-checklist.md --------- Co-authored-by: Esther Kim <[email protected]>
DataDog · May 6, 2024 · d572933 · d572933
1 parent 9015d39
commit d572933
Showing 1 changed file with 29 additions and 17 deletions.
diff --git a/content/en/service_management/service_level_objectives/guide/slo-checklist.md b/content/en/service_management/service_level_objectives/guide/slo-checklist.md
@@ -10,11 +10,11 @@ further_reading:
 - link: 'https://learn.datadoghq.com/courses/intro-to-slo'
   tag: 'Learning Center'
   text: 'Introduction to Service Level Objectives'
+- link: "/service_management/service_level_objectives/guide/slo_types_comparison/"
+  tag: "Documentation"
+  text: "Comparison of Datadog SLO Types"
 ---
 
-<div class="alert alert-info">
-Click <a href="https://www.datadoghq.com/pdf/SLOChecklist_200619.pdf">here</a> to find a PDF version of this page.
-</div>
 
 ## Getting started
 
@@ -33,48 +33,60 @@ Click <a href="https://www.datadoghq.com/pdf/SLOChecklist_200619.pdf">here</a> t
 
 #### Response/Request
 
-|              |                                                                |
+|  Type of SLI |  Description                                                   |
 | ------------ | -------------------------------------------------------------- |
 | Availability | Could the server respond to the request successfully?          |
 | Latency      | How long did it take for the server to respond to the request? |
 | Throughput   | How many requests can be handled?                              |
 
 #### Storage
 
-|              |                                              |
+|  Type of SLI |  Description                                 |
 | ------------ | -------------------------------------------- |
 | Availability | Can the data be accessed on demand?          |
 | Latency      | How long does it take to read or write data? |
 | Durability   | Is the data still there when it is needed?   |
 
 #### Pipeline
 
-|             |                                                                    |
+| Type of SLI |   Description                                                      |
 | ----------- | ------------------------------------------------------------------ |
 | Correctness | Was the right data returned?                                       |
 | Freshness   | How long does it take for new data or processed results to appear? |
 
 ### STEP 2
 
-**Do you require a time-based or count-based SLI?**
+**Do you require an SLI calculation that is time-based or count-based?**
 
-**Time-based SLIs use Datadog monitors**:
+The following SLO types are available in Datadog: 
+
+**Metric-based SLOs**
+
+_Example: 99% of requests should complete in less than 250 ms over a 30-day window._
+
+- Count-based SLI calculation
+- SLI is calculated as the sum of good events divided by the sum of total events
+
+**Monitor-based SLOs**
 
 _Example: the latency of all user requests should be less than 250 ms 99% of the time in any
 30-day window._
 
-1. Select a single monitor,
-2. Select multiple monitors (up to 20), or
-3. Select a single multi alert monitor and pick specific monitor groups (up to 20) to include in
-   the SLO calculation
+- Time-based SLI calculation
+- SLI calculated based on the underlying Monitor’s uptime
+- You can select a single monitor, multiple monitors (up to 20), or a single multi alert monitor with groups
 
 If you need to create a new monitor go to the [Monitor create][2] page.
 
-**Count-based SLIs use metrics in your Datadog account and do not require a monitor**:
+**Time Slice SLOs**
 
-_Example: 99% of requests should complete in less than 250 ms over a 30-day window._
+_Example: the latency of all user requests should be less than 250 ms 99% of the time in any
+30-day window._
+
+- Time-based SLI calculation
+- SLI calculated based on your custom uptime definition using a metric query
 
-## Implementing your SLIs
+## Implement your SLIs
 
 1. [Custom metrics][3] (for example, counters)
 2. [Integration metrics][4] (for example, load balancer, http requests)
@@ -83,8 +95,8 @@ _Example: 99% of requests should complete in less than 250 ms over a 30-day wind
 
 ## Set your target objective and time window
 
-1. Select your target: `99%`, `99.5%`, `99.9%`, `99.95%`, or whatever makes sense for your requirements.
-2. Select your time window: over the last `7`, `30`, or `90 days`
+1. Select your target: `99%`, `99.5%`, `99.9%`, `99.95%`, or any other target value that makes sense for your requirements.
+2. Select your time window: over the last rolling `7`, `30`, or `90 days`
 
 ## Name, describe, and tag your SLOs