add a couple of metrics to the example.json

alexewerlof · Sep 23, 2024 · 020bf5b · 020bf5b
1 parent 4369d8a
commit 020bf5b
Show file tree

Hide file tree

Showing 2 changed files with 36 additions and 14 deletions.
diff --git a/workshop/example.json b/workshop/example.json
@@ -29,9 +29,25 @@
           ],
           "metrics": [
             {
-              "displayName": "Response time",
-              "description": "How long it takes to respond to a request",
-              "measuredFailuresIndex": []
+              "displayName": "response_code between 200-499",
+              "description": "error rate",
+              "measuredFailuresIndex": [
+                0
+              ]
+            },
+            {
+              "displayName": "latency < 10 seconds",
+              "description": "The response to climate API is relatively fast",
+              "measuredFailuresIndex": [
+                0
+              ]
+            },
+            {
+              "displayName": "GET climate successful",
+              "description": "",
+              "measuredFailuresIndex": [
+                1
+              ]
             }
           ]
         },
@@ -48,15 +64,6 @@
               "likelihood": "Rare",
               "impactLevel": "Minor"
             },
-            {
-              "consumerIndex": 1,
-              "consumptionIndex": 1,
-              "symptom": "Can't lock the car",
-              "consequence": "Thieves may get in the car before the user gets to lock it",
-              "businessImpact": "The user may take significant financial damage and take us to court",
-              "likelihood": "Rare",
-              "impactLevel": "Catastrophic"
-            },
             {
               "consumerIndex": 1,
               "consumptionIndex": 1,
@@ -65,9 +72,24 @@
               "businessImpact": "The user may call customer support",
               "likelihood": "Possible",
               "impactLevel": "Insignificant"
+            },
+            {
+              "consumerIndex": 1,
+              "consumptionIndex": 1,
+              "symptom": "Can't lock the car",
+              "consequence": "Thieves may get in the car before the user gets to lock it",
+              "businessImpact": "The user may take significant financial damage and take us to court",
+              "likelihood": "Rare",
+              "impactLevel": "Catastrophic"
             }
           ],
-          "metrics": []
+          "metrics": [
+            {
+              "displayName": "",
+              "description": "",
+              "measuredFailuresIndex": []
+            }
+          ]
         }
       ]
     },

diff --git a/workshop/index.html b/workshop/index.html
@@ -92,7 +92,7 @@ <h2>Why failures?</h2>
                         and there are even more pitfalls.
                     </p>
                     <p>
-                        Our approach is based on the following assumptions:
+                        Our approach is based on the following principles:
                     </p>
                     <ul>
                         <li><em>No vanity metrics</em>: SLI tie to system reliability from the consumers' perspective. If an anomaly does not lead to a consumer facing failure and business risk, it is out of scope.</li>