Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-09 02:17:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update LAB_11-Implement_Monitoring.md

Browse Source
This commit is contained in:
staleycyn 2024-01-02 18:46:09 -08:00 committed by GitHub
parent 80ff0f9e6f
commit c686fd5953
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
New Instructions/Lab/LAB_11-Implement_Monitoring.md
View File

@ -155,17 +155,19 @@ In this task, you trigger the alert and confirm a notification is sent.
1. Select **Delete** from the menu bar. 1. Select **Delete** from the menu bar.
1. Type "yes" in the **Confirm delete** field, then select **Delete**. 1. Check the box for **Apply force delete**. Check the box to acknowledge the deletion, then select **Delete**.
1. In the title bar, select the **Notifications** icon and wait until **vm1** is successfully deleted. 1. In the title bar, select the **Notifications** icon and wait until **vm0** is successfully deleted.
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. 1. You should receive 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-lab11-alert-email.png) ![Screenshot of alert email.](../media/az104-lab11-alert-email.png)
>**Note:** There is no need to wail on the email, continue on.
1. On the Azure portal resource menu, select **Monitor**, and then select **Alerts** in the menu on the left. 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 **vm1**. 1. You should have three verbose alerts that were generated by deleting **vm0**.
1. Select the name of one of the alerts (For example, **VM was deleted**). An **Alert details** pane appears that shows more details about the event. 1. Select the name of one of the alerts (For example, **VM was deleted**). An **Alert details** pane appears that shows more details about the event.
@ -173,9 +175,7 @@ In this task, you trigger the alert and confirm a notification is sent.
In this task, you create an alert rule to suppress notifications during maintenance periods. In this task, you create an alert rule to suppress notifications during maintenance periods.
1. In the Azure portal resource menu, select **Monitor**, select **Alerts** in the menu on the left, and select **Alert processing rules** in the menu bar. 1. Continue in the **Alerts** blade, select **Alert processing rules** and then **+ Create**.
1. Select **+ Create**.
1. Select your **resource group**, then select **Apply**. 1. Select your **resource group**, then select **Apply**.
@ -199,7 +199,7 @@ Enter these settings for the scheduling of the alert processing rule:
| Setting | Value | | Setting | Value |
|---------|---------| |---------|---------|
| Resource group | Select your sandbox resource group. | | Resource group | **az104-rg11** |
| Rule name | `Planned Maintenance` | | Rule name | `Planned Maintenance` |
| Description | `Suppress notifications during planned maintenance.` | | Description | `Suppress notifications during planned maintenance.` |