From faf6511f3b22fc39f4e18b41ecbd8c928bae569e Mon Sep 17 00:00:00 2001 From: Kacey Gambill Date: Sat, 11 Nov 2023 04:10:50 +0000 Subject: [PATCH] fix a whoopsie --- _posts/2023-11-10-alerting-fatigue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2023-11-10-alerting-fatigue.md b/_posts/2023-11-10-alerting-fatigue.md index 6d0e14b..97fd3b6 100644 --- a/_posts/2023-11-10-alerting-fatigue.md +++ b/_posts/2023-11-10-alerting-fatigue.md @@ -66,7 +66,7 @@ With these alerts, they should only be created when we can link to a dashboard o For example, if we alerted on receiving a high rate of errors, I would expect to see a dashboard or runbook indicating that we should look at: - what kind of errors are happening and how many erros are there?? - sum of 500 internal server error -- sum of 500 not implemented +- sum of 501 not implemented - sum of 502 bad gateway - sum of 503 service unavailable - sum of 504 gateway timeout's