From 878743ecc53f11cfe3b691c7c7f2d1dab164c682 Mon Sep 17 00:00:00 2001 From: staleycyn <45440075+staleycyn@users.noreply.github.com> Date: Tue, 19 Dec 2023 05:54:08 -0800 Subject: [PATCH] Update LAB_11-Implement_Monitoring.md --- New Instructions/Lab/LAB_11-Implement_Monitoring.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/New Instructions/Lab/LAB_11-Implement_Monitoring.md b/New Instructions/Lab/LAB_11-Implement_Monitoring.md index a0720082..5e10668f 100644 --- a/New Instructions/Lab/LAB_11-Implement_Monitoring.md +++ b/New Instructions/Lab/LAB_11-Implement_Monitoring.md @@ -152,7 +152,7 @@ To trigger an alert, you need to delete the Linux VM that you created in the pre 1. You should have received a notification email that reads, **Important notice: Azure Monitor alert VM was deleted was activated...** If not, open your email program and look for an email from azure-noreply@microsoft.com. - ![Screenshot of alert email.](../media/az104-11-alert-email.png) + ![Screenshot of alert email.](../media/az104-lab11-alert-email.png) 1. On the Azure portal resource menu, select **Monitor**, and then select **Alerts** in the menu on the left. @@ -179,7 +179,7 @@ Enter these settings for the scheduling of the alert processing rule: |End|Enter tomorrow's date at 7am.| |Time zone|Select the local timezone.| - ![Screenshot of the scheduling section of an alert processing rule](../media/az104-11-alert-processing-rule-schedule.png") + ![Screenshot of the scheduling section of an alert processing rule](../media/az104-lab11-alert-processing-rule-schedule.png) 1. Select **Next: Details** and enter these settings: