From ce5fb29200043a6613c99ea5fb76777cfa211061 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Tue, 2 Jan 2024 18:55:48 -0800
Subject: [PATCH] Update LAB_11-Implement_Monitoring.md

---
 .../Lab/LAB_11-Implement_Monitoring.md        | 22 +++++--------------
 1 file changed, 6 insertions(+), 16 deletions(-)

diff --git a/New Instructions/Lab/LAB_11-Implement_Monitoring.md b/New Instructions/Lab/LAB_11-Implement_Monitoring.md
index 7344540e..d54bfd82 100644
--- a/New Instructions/Lab/LAB_11-Implement_Monitoring.md	
+++ b/New Instructions/Lab/LAB_11-Implement_Monitoring.md	
@@ -163,8 +163,8 @@ In this task, you trigger the alert and confirm a notification is sent.
 
     ![Screenshot of alert email.](../media/az104-lab11-alert-email.png)
 
-   >**Note:** There is no need to wail on the email, continue on. 
-
+   >**Note:** It can take a few minutes for the alert email to be sent and for the alerts to be updated in the portal. If you don't want to wait, continue to the next task and return. 
+   
 1. On the Azure portal resource menu, select **Monitor**, and then select **Alerts** in the menu on the left.
 
 1. You should have three verbose alerts that were generated by deleting **vm0**.
@@ -211,11 +211,11 @@ In this task, you will use Azure Monitor to query the data captured from the vir
 
 1. In the Azure portal, search for and select `Monitor` blade, click **Logs**.
 
-    >**Note**: You might need to click **Get Started** if this is the first time you access Log Analytics. If you still see an **Enable** button, wait for the previous deployment to finish.
+1. In the **Queries** window, select **Virtual machines** (left pane).
 
-1. If necessary, click **Select scope**, on the **Select a scope** blade, expand your subscription, expand resource group **az104-rg1**, then select **az104-vm0**, and click **Apply**.
+1. Notice the canned queries that are available. **Run** the **Count heartbeats** query. 
 
-1. In the query window, paste the following query, click **Run**, and review the resulting chart:
+1. In the query window, replace the query and then click **Run**, and review the resulting chart:
 
    ```sh
    // Virtual Machine available memory
@@ -226,17 +226,7 @@ In this task, you will use Azure Monitor to query the data captured from the vir
    | project TimeGenerated, Name, Val
    | render timechart
    ```
-
-    > **Note**: The query should not have any errors (indicated by red blocks on the right scroll bar). If the query will not paste without errors, paste the query code into a text editor such as Notepad, and then copy and paste it into the query window from there.
-
-
-1. Click **Queries** in the toolbar, 
-
-    >**Note**: Depending on your screen resolution, **Queries** might be hidden behind an elipses.
-
-1. Clear any existing filters. Using the query search, search for `Track VM Availability using Heartbeat` then select **Run**.
-
-1. Select the **Results** tab of the query and review the results of the query.
+1. As you have time, review and run other queries. Notice you can configure an alert rule based on a query. 
 
 ## Review the main points of the lab