Azure Monitor overview - Commands & Configuration

Introduction

Azure Monitor helps you see what is happening with your cloud apps and resources. It collects data and shows you useful information to keep your systems healthy and running smoothly.

When you want to track how well your website or app is performing in real time.

When you need to find out why a cloud service is slow or not working.

When you want to get alerts if something goes wrong with your cloud resources.

When you want to collect logs and metrics from different Azure services in one place.

When you want to analyze trends and usage patterns to improve your cloud setup.

Commands

This command creates a Log Analytics workspace where Azure Monitor stores collected data. You need this workspace to start monitoring your resources.

Terminal

az monitor log-analytics workspace create --resource-group example-group --workspace-name example-workspace --location eastus

Expected Output

{

  "customerId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",

  "location": "eastus",

  "name": "example-workspace",

  "resourceGroup": "example-group",

  "sku": {

    "name": "PerGB2018"

  },

  "type": "Microsoft.OperationalInsights/workspaces"

}

→

--resource-group - Specifies the Azure resource group to create the workspace in

→

--workspace-name - Names the Log Analytics workspace

→

--location - Sets the Azure region for the workspace

This command lists the types of metrics you can collect from a specific Azure resource, here a virtual machine. It helps you know what data you can monitor.

Terminal

az monitor metrics list-definitions --resource /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-group/providers/Microsoft.Compute/virtualMachines/example-vm

Expected Output

{

  "value": [

    {

      "name": {

        "value": "Percentage CPU",

        "localizedValue": "Percentage CPU"

      },

      "unit": "Percent"

    },

    {

      "name": {

        "value": "Network In",

        "localizedValue": "Network In"

      },

      "unit": "Bytes"

    }

  ]

}

→

--resource - Specifies the Azure resource to get metric definitions for

This command retrieves the current values of the 'Percentage CPU' metric for the virtual machine, updated every minute. It shows how busy the CPU is.

Terminal

az monitor metrics list --resource /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-group/providers/Microsoft.Compute/virtualMachines/example-vm --metric "Percentage CPU" --interval PT1M

Expected Output

{

  "cost": 0,

  "timeseries": [

    {

      "data": [

        {

          "timeStamp": "2024-06-01T12:00:00Z",

          "average": 15.5

        },

        {

          "timeStamp": "2024-06-01T12:01:00Z",

          "average": 18.2

        }

      ]

    }

  ]

}

→

--metric - Specifies which metric to retrieve

→

--interval - Sets the time interval for metric data points

→

--resource - Specifies the Azure resource to get metrics from

This command creates an alert that triggers when the average CPU usage goes above 80%. Alerts help you react quickly to problems.

Terminal

az monitor alert create --name HighCPUAlert --resource-group example-group --scopes /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-group/providers/Microsoft.Compute/virtualMachines/example-vm --condition "avg Percentage CPU > 80" --description "Alert when CPU usage is over 80%" --action-group example-action-group

Expected Output

{

  "name": "HighCPUAlert",

  "resourceGroup": "example-group",

  "description": "Alert when CPU usage is over 80%",

  "enabled": true

}

→

--condition - Defines the rule that triggers the alert

→

--scopes - Specifies which resource the alert monitors

→

--action-group - Defines who or what gets notified when the alert fires

Key Concept

If you remember nothing else from this pattern, remember: Azure Monitor collects data from your cloud resources and helps you see and react to their health and performance.

Common Mistakes

Trying to get metrics without creating a Log Analytics workspace first

Azure Monitor needs a workspace to store and query monitoring data

Always create a Log Analytics workspace before collecting or querying metrics

Using incorrect resource IDs in commands

Commands fail if the resource path is wrong or does not exist

Copy the full resource ID exactly from the Azure portal or CLI

Setting alert conditions with wrong syntax

Alerts won't create or won't trigger if the condition syntax is invalid

Use the correct condition format like "avg Percentage CPU > 80"

Summary

Create a Log Analytics workspace to store monitoring data.

List available metrics for your Azure resources to know what you can monitor.

Retrieve current metric values to check resource performance.

Set alerts to get notified when important metrics cross thresholds.

Practice

1. What is the main purpose of Azure Monitor?

easy

A. To watch cloud resources and keep them healthy

B. To create virtual machines

C. To store large amounts of data

D. To manage user permissions

Solution

1. Step 1: Understand Azure Monitor's role

   Azure Monitor watches cloud resources to ensure they work well and stay healthy.

2. Step 2: Compare options with this role

   Creating virtual machines, storing data, and managing permissions are not the main tasks of Azure Monitor.

3. Final Answer:

   To watch cloud resources and keep them healthy -> Option A

4. Quick Check:

   Azure Monitor = watches resources [OK]

Hint: Azure Monitor = watches and keeps resources healthy [OK]

Common Mistakes:

• Confusing Azure Monitor with storage services
• Thinking it creates virtual machines
• Mixing it up with user management

2. Which of the following is the correct way to enable Azure Monitor for a resource in the Azure portal?

easy

A. Disable all alerts to start Azure Monitor

B. Create a new virtual machine and Azure Monitor is enabled by default

C. Go to the resource, select 'Monitoring', then 'Insights', and enable monitoring

D. Run a PowerShell script to delete monitoring settings

Solution

1. Step 1: Check how to enable monitoring in Azure portal

   Azure Monitor is enabled by going to the resource, selecting 'Monitoring', then 'Insights', and turning it on.

2. Step 2: Eliminate incorrect options

   Creating a VM does not automatically enable Azure Monitor; deleting monitoring or disabling alerts does not enable it.

3. Final Answer:

   Go to the resource, select 'Monitoring', then 'Insights', and enable monitoring -> Option C

4. Quick Check:

   Enable monitoring via Insights in portal [OK]

Hint: Enable monitoring under resource's Insights tab [OK]

Common Mistakes:

• Assuming Azure Monitor is on by default for all resources
• Confusing enabling with disabling alerts
• Thinking deleting settings enables monitoring

3. Consider this Azure Monitor alert rule setup:
Alert when CPU usage > 80% for 5 minutes
What happens if CPU usage spikes to 85% for 3 minutes and then drops to 75%?

medium

A. An alert is triggered immediately when CPU hits 85%

B. No alert is triggered because the high CPU lasted less than 5 minutes

C. An alert triggers after CPU usage drops below 80%

D. The alert triggers only if CPU stays above 90%

Solution

1. Step 1: Understand alert condition timing

   The alert triggers only if CPU usage stays above 80% continuously for 5 minutes.

2. Step 2: Analyze the CPU usage pattern

   The CPU was above 80% for only 3 minutes, then dropped below, so the alert condition is not met.

3. Final Answer:

   No alert is triggered because the high CPU lasted less than 5 minutes -> Option B

4. Quick Check:

   Alert needs 5 minutes above threshold [OK]

Hint: Alert triggers only after condition lasts full time [OK]

Common Mistakes:

• Thinking alert triggers immediately on spike
• Ignoring the 5-minute duration condition
• Confusing threshold values

4. You set up an Azure Monitor alert but it never triggers even when the condition is met. What is a likely cause?

medium

A. Alert rule is disabled or not properly configured

B. Azure Monitor does not support alerts

C. The resource is offline and cannot be monitored

D. Alerts only work during business hours

Solution

1. Step 1: Check alert rule status

   If the alert rule is disabled or misconfigured, it will not trigger even if conditions are met.

2. Step 2: Review other options for correctness

   Azure Monitor supports alerts anytime; resources offline may not send data but usually cause other errors; alerts are not time-limited.

3. Final Answer:

   Alert rule is disabled or not properly configured -> Option A

4. Quick Check:

   Disabled alert rules never trigger [OK]

Hint: Check if alert rule is enabled and correct [OK]

Common Mistakes:

• Assuming Azure Monitor can't alert
• Thinking alerts depend on time of day
• Ignoring alert rule configuration

5. You want to reduce costs but keep monitoring important metrics with Azure Monitor. Which approach is best?

hard

A. Collect all possible data and create alerts for every metric

B. Disable Azure Monitor completely to save money

C. Use Azure Monitor only during peak hours

D. Configure sampling to collect fewer data points and set alerts only on critical metrics

Solution

1. Step 1: Understand cost-saving options in Azure Monitor

   Sampling reduces data volume by collecting fewer points, lowering cost. Alerting only on critical metrics avoids unnecessary alerts.

2. Step 2: Evaluate other options

   Disabling monitoring risks missing issues; collecting all data increases cost; limiting monitoring by time is not supported and risky.

3. Final Answer:

   Configure sampling to collect fewer data points and set alerts only on critical metrics -> Option D

4. Quick Check:

   Sampling + critical alerts = cost saving [OK]

Hint: Use sampling and alert only on key metrics [OK]

Common Mistakes:

• Turning off monitoring completely
• Collecting too much data without filtering
• Assuming monitoring can be time-limited