Lab answer key: Implementing operational monitoring in hybrid scenarios

Note: An interactive lab simulation is available that allows you to click through this lab at your own pace. You may find slight differences between the interactive simulation and the hosted lab, but the core concepts and ideas being demonstrated are the same.

Exercise 1: Preparing a monitoring environment

Task 1: Deploy an Azure virtual machine

  1. Connect to SEA-SVR2, and if needed, sign in as CONTOSO\Administrator with the password Pa55w.rd.
  2. On SEA-SVR2, start Microsoft Edge, go to the Azure portal, and sign in by using the credentials of a user account with the Owner role in the subscription you’ll be using in this lab.
  3. On SEA-SVR2, in the Microsoft Edge window displaying the Azure portal, open the Azure Cloud Shell pane by selecting the Cloud Shell button in the Azure portal.
  4. If prompted to select either Bash or PowerShell, select PowerShell.

    Note: If this is the first time you’re starting Cloud Shell and you’re presented with the You have no storage mounted message, select the subscription you are using in this lab, and then select Create storage.

  5. In the toolbar of the Cloud Shell pane, select the Upload/Download files icon, in the drop-down menu select Upload, and upload the file C:\Labfiles\Lab09\L09-rg_template.json into the Cloud Shell home directory.
  6. Repeat the previous step to upload the C:\Labfiles\Lab09\L09-rg_template.parameters.json file into the Cloud Shell home directory.
  7. To create the resource group that will be hosting the lab environment, in the PowerShell session in the Cloud Shell pane, enter the following commands, and after entering each command, press Enter (replace the <Azure_region> placeholder with the name of an Azure region where you intend to deploy resources in this lab):

    Note: You can use the (Get-AzLocation).Location command to list the names of available Azure regions:

    $location = '<Azure_region>'
    $rgName = 'AZ801-L0901-RG'
    New-AzResourceGroup -ResourceGroupName $rgName -Location $location
    
  8. To deploy an Azure virtual machine (VM) into the newly created resource group, enter the following command and press Enter:

    New-AzResourceGroupDeployment -Name az801l0901deployment -ResourceGroupName $rgName -TemplateFile ./L09-rg_template.json -TemplateParameterFile ./L09-rg_template.parameters.json -AsJob
    

    Note: Do not wait for the deployment to complete but instead proceed to the next task. The deployment should take about 3 minutes.

Task 2: Register the Microsoft.Insights and Microsoft.AlertsManagement resource providers

  1. To register the Microsoft.Insights and Microsoft.AlertsManagement resource providers, on SEA-SVR2, from the Cloud Shell pane, enter the following commands, and after entering each command, press Enter.

    Register-AzResourceProvider -ProviderNamespace Microsoft.Insights
    Register-AzResourceProvider -ProviderNamespace Microsoft.AlertsManagement
    

    Note: To verify the registration status, you can use the Get-AzResourceProvider cmdlet.

    Note: Do not wait for the registration process to complete but instead proceed to the next task. The registration should take about 3 minutes.

  2. Close Cloud Shell.

Task 3: Create and configure an Azure Log Analytics workspace

  1. On SEA-SVR2, in the Azure portal, in the Search resources, services, and docs text box, in the toolbar, search for and select Log Analytics workspaces, and then, from the Log Analytics workspaces page, select + Create.
  2. On the Basics tab of the Create Log Analytics workspace page, enter the following settings, select Review + Create, and then select Create:

    Settings Value
    Subscription the name of the Azure subscription you are using in this lab
    Resource group the name of a new resource group AZ801-L0902-RG
    Log Analytics Workspace any unique name
    Region the name of the Azure region into which you deployed the virtual machine in the previous task

    Note: Make sure that you specify the same region into which you deployed virtual machines in the previous task.

    Note: Wait for the deployment to complete. The deployment should take about 1 minute.

  3. In the Azure portal, navigate to the blade of the newly provisioned workspace.
  4. On the workspace blade, navigate to the Agents management blade and record the values of the Workspace ID and Primary key. You will need them in the next exercise.

Task 4: Install Service Map solution

  1. On SEA-SVR2, in the Azure portal, in the Search resources, services, and docs text box, in the toolbar, search for Service Map and, in the list of results, in the Marketplace section, select Service Map.
  2. On the Create Service Map Solution blade, on the Select Workspace tab, specify the following settings, select Review + Create, and then select Create:

    Settings Value
    Subscription the name of the Azure subscription you are using in this lab
    Resource group AZ801-L0902-RG
    Log Analytics Workspace the name of the Log Analytics workspace you created in the previous task

Exercise 2: Configuring monitoring of on-premises servers

Task 1: Install the Log Analytics agent and the Dependency agent

  1. While connected to the console session on SEA-SVR2, in the browser window displaying the Azure portal, on the Agents management blade, select the Download Windows Agent (64 bit) link to download the 64-bit Windows Log Analytics agent.
  2. Once the download of the agent installer is completed, click the downloaded file to start the setup wizard.
  3. On the Welcome page, select Next.
  4. On the License Terms page, read the license and then select I Agree.
  5. On the Destination Folder page, change or keep the default installation folder and then select Next.
  6. On the Agent Setup Options page, select Connect the agent to Azure Log Analytics checkbox and then select Next.
  7. On the Azure Log Analytics page, enter the Workspace ID and Workspace Key (Primary Key) you recorded in the previous exercise.
  8. Select Next once you have completed providing the necessary configuration settings.
  9. On the Ready to Install page, review your choices and then select Install.
  10. On the Configuration completed successfully page, select Finish.
  11. On SEA-SVR2, start Windows PowerShell as administrator.
  12. From the Administrator: Windows PowerShell console, run the following commands to install Dependency Agent:

    Invoke-WebRequest "https://aka.ms/dependencyagentwindows" -OutFile InstallDependencyAgent-Windows.exe
    .\InstallDependencyAgent-Windows.exe /S
    

Exercise 3: Configuring monitoring of Azure VMs

Task 1: Review host-based monitoring

  1. In the Azure portal, search for and select Virtual machines, and on the Virtual machines page, select az801l09-vm0.
  2. On the az801l09-vm0 page, in the Monitoring section, select Metrics.
  3. On the az801l09-vm0 | Metrics page, on the default chart, in the Metric Namespace drop-down list, note that only Virtual Machine Host metrics are available.

    Note: This is expected because no guest-level diagnostic settings have been configured yet. However, you do have the option of enabling guest memory metrics directly from the Metric Namespace drop-down list. You will enable it later in this exercise.

  4. In the Metric drop-down list, review the list of available metrics.

    Note: The list includes a range of CPU, disk, and network-related metrics that can be collected from the virtual machine host without having access into guest-level metrics.

  5. In the Metric drop-down list, select Percentage CPU, in the Aggregation drop-down list, ensure that the Avg entry is selected, and review the resulting chart.

Task 2: Configure diagnostic settings and VM Insights

  1. On the az801l09-vm0 page, in the Monitoring section, select Diagnostic settings.
  2. On the Overview tab of the az801l09-vm0 | Diagnostic settings page, select Enable guest-level monitoring.

    Note: Wait for the operation to take effect. This might take about 3 minutes.

  3. Switch to the Performance counters tab of the az801l09-vm0 | Diagnostic settings page 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.

  4. Switch to the Logs tab of the az801l09-vm0 | Diagnostic settings page and select the Enable guest-level monitoring button.

    Note: Wait until the guest-level monitoring diagnostics are enabled. This should take about 3 minutes.

  5. On the az801l09-vm0 | Diagnostic settings page, on the Overview tab, 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. You can customize them from the Logs tab.

  6. On the az801l09-vm0 | Diagnostic settings page, select the Logs tab and review the available configuration settings.
  7. On the az801l09-vm0 | Logs page, on the vertical menu on the left side, in the Monitoring section, select Metrics.
  8. On the az801l09-vm0 | Metrics page, on the default chart, note that at this point, the Metric Namespace drop-down list, in addition to the Virtual Machine Host entry, also includes the Guest (classic) entry.

    Note: This is expected because you enabled guest-level diagnostic settings. You also have the Enable new guest memory metrics option.

  9. In the Metric Namespace drop-down list, select the Guest (classic) entry.
  10. In the Metric drop-down list, review the list of available metrics and note that they include a range of metrics related to memory and logical disks.

    Note: The list includes additional guest-level metrics not available when relying on the host-level monitoring only.

  11. In the Metric Namespace drop-down list, select the Enable new guest memory metrics entry.
  12. In the Enable Guest Metrics (Preview) pane, review the provided information.
  13. On the az801l09-vm0 | Diagnostic settings page, select the Sinks tab, in the Azure Monitor (Preview) section, select Enabled, and then select Save.

    Note: Select the warning notification box below the Azure Monitor (Preview) section to activate the Enabled button.

  14. Browse back to the az801l09-vm0 | Metrics page, on the default chart, note that at this point, the Metric Namespace drop-down list, in addition to the Virtual Machine Host and Guest (classic) entries, also includes the Virtual Machine Guest entry.

    Note: You might need to refresh the page for the Virtual Machine Guest entry to appear.

  15. On the az801l09-vm0 | Metrics page, on the vertical menu on the left side, in the Monitoring section, select Logs.
  16. If needed, on the az801l09-vm0 | Logs page, select Enable.
  17. In the Choose a Log Analytics Workspace drop-down list, select the Log Analytics workspace you created earlier in this lab, and then select Enable.
  18. On the az801l09-vm0 | Logs page, on the vertical menu on the left side, in the Monitoring section, select Insights.
  19. If needed, on the az801l09-vm0 | Insights page, select Enable.

    Note: This setting provides the Azure VM Insights functionality. VM Insights is an Azure Monitor solution that facilitates monitoring performance and health of both Azure VMs and on-premises computers running Windows or Linux.

  20. On SEA-SVR2, in the Azure portal, in the Search resources, services, and docs text box, in the toolbar, search for and select Monitor, and then, on the Monitor | Overview page, under Insights, select VM insights.
  21. On the Monitor | Virtual Machines page, select the Performance tab, and if needed, select Try now.
  22. On the Monitor | Virtual Machines page, select the Map tab, and then select Try now.
  23. On the Manage Coverage page, select Configure Workspace.
  24. On the Azure Monitor page, from the Choose a Log Analytics Workspace drop-down menu, select the workspace you created earlier in this lab, and then select Configure.

    Note: This option enables monitoring and alerting capabilities using health model, which consists of a hierarchy of health monitors built using the metrics emitted by Azure Monitor for VMs.

Exercise 4: Evaluating monitoring services

Task 1: Review Azure Monitor monitoring and alerting functionality

  1. On SEA-SVR2, in the Azure portal, browse back to the Monitor | Metrics page.
  2. On the Select a scope page, on the Browse tab, browse to the AZ801-L0901-RG resource group, expand it, select the checkbox next to the az801l09-vm0 virtual machine entry within that resource group, and then select Apply.

    Note: If you do not see az801l09-vm0 in the list, in the Search to filter items… box, search for az801l09-vm0.

    Note: This gives you the same view and options as those available from the az801l09-vm0 | Metrics page.

  3. In the Metric drop-down list, select Percentage CPU, ensure that Avg appears in the Aggregation drop-down list, and review the resulting chart.
  4. On the Monitor | Metrics page, in the Avg Percentage CPU for az801l09-vm0 pane, select 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.

  5. On the Create an alert rule page, in the Condition section, select the existing condition entry.
  6. On the Configure signal logic page, in the list of signals, in the Alert logic section, specify the following settings (leave others with their default values), and then select Done:

    Settings Value
    Threshold Static
    Operator Greater than
    Aggregation type Average
    Threshold value 2
    Aggregation granularity (Period) 1 minute
    Frequency of evaluation Every 1 Minute
  7. On the Create an alert rule page, on the Actions tab, select the + Create action group button.
  8. On the Basics tab of the Create an action group page, specify the following settings (leave others with their default values), and then select Next: Notifications >:

    Settings Value
    Subscription the name of the Azure subscription you are using in this lab
    Resource group AZ801-L0902-RG
    Action group name az801l09-ag1
    Display name az801l09-ag1
  9. On the Notifications tab of the Create an action group page, in the Notification type drop-down list, select Email/SMS message/Push/Voice. In the Name text box, type admin email, and then select the Edit details (pencil) icon.
  10. On the Email/SMS message/Push/Voice page, select the Email checkbox, type your email address in the Email textbox, leave others with their default values, and then select OK. Back on the Notifications tab of the Create an action group page, select Next: Actions >.
  11. On the Actions tab of the Create an action group page, review items available in the Action type drop-down list without making any changes and select Review + create.
  12. On the Review + create tab of the Create an action group page, select Create.
  13. Back on the Create an alert rule page, in the Alert rule details section, specify the following settings (leave others with their default values):

    Settings Value
    Alert rule name CPU Percentage above the test threshold
    Description CPU Percentage above the test threshold
    Resource group AZ801-L0902-RG
    Severity Sev 3
    Enable rule upon creation Yes
  14. Select Create alert rule.

    Note: It can take up to 10 minutes for a metric alert rule to become active.

  15. In the Azure portal, search for and select Virtual machines, and on the Virtual machines page, select az801l09-vm0.
  16. On the az801l09-vm0 page, in the Operations section, select Run command, and then select RunPowerShellScript.
  17. On the Run Command Script page, in the PowerShell Script section, enter the following commands and select Run to increase the CPU utilization within the target operating system:

    $vCpuCount = Get-WmiObject Win32_Processor | Select-Object -ExpandProperty NumberOfLogicalProcessors
    ForEach ($vCpu in 1..$vCpuCount){ 
       Start-Job -ScriptBlock{
          $result = 1;
          ForEach ($loopCount in 1..2147483647){
             $result = $result * $loopCount
          }
       }
    }
    

    Note: This should increase the CPU utilization above the threshold of the newly created alert rule.

  18. On SEA-SVR2, in the Microsoft Edge window displaying the Azure portal, open another tab, browse to the Monitor page, and then select Alerts.
  19. Note the number of Sev 3 alerts, and then select the Sev 3 row.

    Note: You might need to wait for a few minutes and select Refresh.

  20. On the All Alerts page, review generated alerts.

Task 2: Review Azure Monitor VM Insights functionality

  1. On SEA-SVR2, in the Azure portal, browse back to the az801l09-vm0 virtual machine page.
  2. On the az801l09-vm0 virtual machine page, on the vertical menu on the left side, in the Monitoring section, select Insights.
  3. On the az801l09-vm0 | Insights page, on the Performance tab, review the default set of metrics, including logical disk performance, CPU utilization, available memory, as well as bytes sent and received rates.
  4. On the az801l09-vm0 | Insights page, select the Map tab and review the autogenerated map.
  5. On the az801l09-vm0 | Insights page, select the Health tab and review its content.

    Note: The availability of health information is dependent on completion of the workspace upgrade.

Task 3: Review Azure Log Analytics functionality

  1. On SEA-SVR2, in the Azure portal, browse back to the Monitor page and select Logs.

    Note: You might need to close the Welcome to Log Analytics pane if this is the first time you access Log Analytics.

  2. On the Select a scope page, select the Recent tab, select the unique workspace you created earlier in this lab, and then select Apply.
  3. In the query window, paste the following query, select Run, and review the resulting chart:

    // Virtual Machine available memory
    // Chart the VM's available memory over the last hour.
    InsightsMetrics
    | where TimeGenerated > ago(1h)
    | where Name == "AvailableMB"
    | project TimeGenerated, Name, Val
    | render timechart
    
  4. Select Queries in the toolbar, in the Queries pane, expand the Virtual Machines node, select Track VM availability tile, select the Run button, and review the results.
  5. On the New Query 1 tab, select the Tables header, and review the list of tables in the Azure Monitor for VMs section.

    Note: The names of several tables correspond to the solutions you installed earlier in this lab. In particular, InsightMetrics is used by Azure VM Insights to store performance metrics.

  6. Move the cursor over the VMComputer entry, select the See Preview data icon, and review the results.

    Note: Verify that the data includes entries for both az801l09-vm0 and SEA-SVR2.contoso.com.

    Note: You might need to wait a few minutes before the update data becomes available.

  7. On SEA-SVR2, in the Azure portal, in the Search resources, services, and docs text box, in the toolbar, search for and select Log Analytics workspaces, and then, from the Log Analytics workspaces page, select the entry representing the workspace you created earlier in this lab.
  8. On the workspace page, on the vertical menu on the left side, in the General section, select Solutions.
  9. In the list of solutions, select ServiceMap, and then, on the Summary page, select the Service Map tile.
  10. On the ServiceMap page, on the Machines tab, select SEA-SVR2 to display is service map.
  11. Zoom in to review the map illustrating the network ports available on SEA-SVR2, select different ports and review the corresponding connection information.
  12. For each connection, switch between the Summary and Properties views, with the latter providing more detailed information regarding connection targets.

Exercise 5: Deprovisioning the Azure environment

Task 1: Start a PowerShell session in Cloud Shell

  1. On SEA-SVR2, in the Microsoft Edge window displaying the Azure portal, open the Cloud Shell pane by selecting the Cloud Shell icon.

Task 2: Delete all Azure resources provisioned in the lab

  1. From the Cloud Shell pane, run the following command to list all resource groups created in this lab:

    Get-AzResourceGroup -Name 'AZ801-L09*'
    

    Note: Verify that the output contains only the resource group you created in this lab. This group will be deleted in this task.

  2. Run the following command to delete all resource groups you created in this lab:

    Get-AzResourceGroup -Name 'AZ801-L09*' | Remove-AzResourceGroup -Force -AsJob
    

    Note: The command executes asynchronously (as determined by the -AsJob parameter). So, while you’ll be able to run another PowerShell command immediately afterwards within the same PowerShell session, it will take a few minutes before the resource groups are actually removed.