From df8c48dd6c862019f10d66b0968b048f6ba2f712 Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Tue, 3 Oct 2023 02:27:35 +0000
Subject: [PATCH] Deployed 3e49d02 with MkDocs version: 1.2.3

---
 .../introduction/index.html                   |   2 +-
 sitemap.xml.gz                                | Bin 1206 -> 1206 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/level101/metrics_and_monitoring/introduction/index.html b/level101/metrics_and_monitoring/introduction/index.html
index e623e40b..ee8f6f92 100644
--- a/level101/metrics_and_monitoring/introduction/index.html
+++ b/level101/metrics_and_monitoring/introduction/index.html
@@ -2368,7 +2368,7 @@ <h2 id="why-is-monitoring-important">Why is monitoring important?</h2>
      Each alert has a set of rules for identifying such anomalies.
      Today many metrics servers such as
      <a href="https://github.com/grafana/grafana">Grafana</a> support alert
-     management. We discuss alerting <a href="#proactive-monitoring-using-alerts">in detail
+     management. We discuss alerting <a href="https://linkedin.github.io/school-of-sre/level101/metrics_and_monitoring/alerts/">in detail
      later</a>. Examples are
      <a href="https://github.com/grafana/grafana">Grafana</a> and
      <a href="https://icinga.com/">Icinga</a>.</p>
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 66b0685c4b1036e3bcb99b1bf527624a8f2ba0a0..9a880648542a6c6797a02d68bd6951fe2d54abcc 100644
GIT binary patch
delta 15
WcmdnSxs8)ezMF$Xyk;ZY1{MG!<ODqc

delta 15
WcmdnSxs8)ezMF$1xOyYo1{MG$M+A5P