From 701ce81b5b95966a3292152e30d1b6b539ab6069 Mon Sep 17 00:00:00 2001 From: Roman Korecky Date: Wed, 5 May 2021 21:01:11 +0200 Subject: [PATCH 1/4] Fixed formatting issue --- Instructions/Labs/LAB_07-Manage_Azure_Storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md index 47c38aa5..f306d70f 100644 --- a/Instructions/Labs/LAB_07-Manage_Azure_Storage.md +++ b/Instructions/Labs/LAB_07-Manage_Azure_Storage.md @@ -210,7 +210,7 @@ In this task, you will configure authentication and authorization for Azure Stor In this task, you will create and configure Azure Files shares. - > **Note**: Before you start this task, verify that the virtual machine you provisioned in the first task of this lab is running. +> **Note**: Before you start this task, verify that the virtual machine you provisioned in the first task of this lab is running. 1. In the Azure portal, navigate back to the blade of the storage account you created in the first task of this lab and, in the **File service** section, click **File shares**. From 179b2ed572273f7aa2833cad249b6de42fb3dd9e Mon Sep 17 00:00:00 2001 From: Roman Korecky Date: Wed, 5 May 2021 21:05:26 +0200 Subject: [PATCH 2/4] Fixed missing escape character on | symbol. The HTML output was not rendered correctly. --- Instructions/Labs/LAB_11-Implement_Monitoring.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index 58003275..aaeaac9e 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -135,7 +135,7 @@ In this task, you will review default monitoring settings of Azure virtual machi 1. On the **az104-11-vm0** blade, in the **Monitoring** section, click **Metrics**. -1. On the **az104-11-vm0 | Metrics** blade, on the default chart, note that the only available **Metrics Namespace** is **Virtual Machine Host**. +1. On the **az104-11-vm0 \| Metrics** blade, on the default chart, note that the only available **Metrics Namespace** is **Virtual Machine Host**. >**Note**: This is expected, since no guest-level diagnostic settings have been configured yet. You do have, however, the option of enabling guest memory metrics directly from the **Metrics Namespace** drop down-list. You will enable it later in this exercise. @@ -151,15 +151,15 @@ In this task, you will configure Azure virtual machine diagnostic settings. 1. On the **az104-11-vm0** blade, in the **Monitoring** section, click **Diagnostic settings**. -1. On the **Overview** tab of the **az104-11-vm0 | Diagnostic settings** blade, click **Enable guest-level monitoring**. +1. On the **Overview** tab of the **az104-11-vm0 \| Diagnostic settings** blade, click **Enable guest-level monitoring**. >**Note**: Wait for the operation to take effect. This might take about 3 minutes. -1. Switch to the **Performance counters** tab of the **az104-11-vm0 | Diagnostic settings** blade and review the available counters. +1. Switch to the **Performance counters** tab of the **az104-11-vm0 \| Diagnostic settings** blade and review the available counters. >**Note**: By default, CPU, memory, disk, and network counters are enabled. You can switch to the **Custom** view for more detailed listing. -1. Switch to the **Logs** tab of the **az104-11-vm0 | Diagnostic settings** blade and review the available event log collection options. +1. Switch to the **Logs** tab of the **az104-11-vm0 \| Diagnostic settings** blade and review the available event log collection options. >**Note**: By default, log collection includes critical, error, and warning entries from the Application Log and System log, as well as Audit failure entries from the Security log. Here as well you can switch to the **Custom** view for more detailed configuration settings. @@ -169,9 +169,9 @@ In this task, you will configure Azure virtual machine diagnostic settings. >**Note**: Do not wait for the operation to complete but instead proceed to the next step. The operation might take about 5 minutes. -1. On the **az104-11-vm0 | Logs** blade, in the **Monitoring** section, click **Metrics**. +1. On the **az104-11-vm0 \| Logs** blade, in the **Monitoring** section, click **Metrics**. -1. On the **az104-11-vm0 | Metrics** blade, on the default chart, note that at this point, the **Metrics Namespace** drop-down list, in addition to the **Virtual Machine Host** entry includes also the **Guest (classic)** entry. +1. On the **az104-11-vm0 \| Metrics** blade, on the default chart, note that at this point, the **Metrics Namespace** drop-down list, in addition to the **Virtual Machine Host** entry includes also the **Guest (classic)** entry. >**Note**: This is expected, since you enabled guest-level diagnostic settings. You also have the option to **Enable new guest memory metrics**. @@ -185,7 +185,7 @@ In this task, you will configure Azure virtual machine diagnostic settings. #### Task 6: Review Azure Monitor functionality -1. In the Azure portal, search for and select **Monitor** and, on the **Monitor | Overview** blade, click **Metrics**. +1. In the Azure portal, search for and select **Monitor** and, on the **Monitor \| Overview** blade, click **Metrics**. 1. On the **Select a scope** blade, on the **Browse** tab, navigate to the **az104-11-rg0** resource group, expand it, select the checkbox next to the **az104-11-vm0** virtual machine entry within that resource group, and click **Apply**. @@ -193,7 +193,7 @@ In this task, you will configure Azure virtual machine diagnostic settings. 1. In the **Metric** drop-down list, select **Percentage CPU**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart. -1. On the **Monitor | Metrics** blade, on the **Avg Percentage CPU for az104-11-vm0** pane, click **New alert rule**. +1. On the **Monitor \| Metrics** blade, on the **Avg Percentage CPU for az104-11-vm0** pane, click **New alert rule**. >**Note**: Creating an alert rule from Metrics is not supported for metrics from the Guest (classic) metric namespace. This can be accomplished by using Azure Resource Manager templates, as described in the document [Send Guest OS metrics to the Azure Monitor metric store using a Resource Manager template for a Windows virtual machine](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/collect-custom-metrics-guestos-resource-manager-vm) From 9bacabec558a6d6ba25a4e105d1ce040d9ead451 Mon Sep 17 00:00:00 2001 From: Roman Korecky Date: Wed, 5 May 2021 21:12:26 +0200 Subject: [PATCH 3/4] Clarification on how to configure the action group. --- Instructions/Labs/LAB_11-Implement_Monitoring.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index aaeaac9e..98d5e282 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -221,9 +221,9 @@ In this task, you will configure Azure virtual machine diagnostic settings. | Action group name | **az104-11-ag1** | | Display name | **az104-11-ag1** | -1. On the **Notifications** tab of the **Create action group** blade, in the **Notification type** drop-down list, select **Email/SMS/Push/Voice**. +1. On the **Notifications** tab of the **Create action group** blade, in the **Notification type** drop-down list, select **Email/SMS/Push/Voice**. In the **Name** text box, type **admin email**. Click the **Edit details** (pencil) icon. -1. On the **Email/SMS/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create action group** blade, in the **Name** text box, type **admin email** and select **Next: Actions >**: +1. On the **Email/SMS/Push/Voice** blade, select the **Email** checkbox, type your email address in the **Email** textbox, leave others with their default values, click **OK**, back on the **Notifications** tab of the **Create action group** blade, select **Next: Actions >**. 1. On the **Actions** tab of the **Create action group** blade, review items available in the **Action type** drop-down list without making any changes and select **Review + create**. From 43e571abb40a688925ae83a9c78a4d77a7220c9e Mon Sep 17 00:00:00 2001 From: Roman Korecky Date: Wed, 5 May 2021 21:20:12 +0200 Subject: [PATCH 4/4] Fixed text in UI. --- Instructions/Labs/LAB_11-Implement_Monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Instructions/Labs/LAB_11-Implement_Monitoring.md b/Instructions/Labs/LAB_11-Implement_Monitoring.md index 98d5e282..0758b467 100644 --- a/Instructions/Labs/LAB_11-Implement_Monitoring.md +++ b/Instructions/Labs/LAB_11-Implement_Monitoring.md @@ -300,7 +300,7 @@ In this task, you will configure Azure virtual machine diagnostic settings. 1. Hover the mouse over the **VMComputer** entry and click the **Preview data** icon. -1. If any data is available, in the **Update** pane, click **See in query editor**. +1. If any data is available, in the **Update** pane, click **Use in editor**. >**Note**: You might need to wait a few minutes before the update data becomes available.