Metrics for resource performance in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to retrieve CPU usage metric for an Azure VM.

Azure

az monitor metrics list --resource [1] --metric "Percentage CPU"

Drag options to blanks, or click blank then click option'

AmyResourceGroup/myVM

B/subscriptions/123/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM

CmyVM

DresourceGroup/myVM

Attempts:

3 left

💡 Hint

Common Mistakes

Using only the VM name without full resource path

Using resource group and VM name separated by slash without full path

The full resource ID is required to specify the Azure VM resource when retrieving metrics.

2fill in blank

medium

Complete the code to filter metrics by time range in Azure CLI.

Azure

az monitor metrics list --resource [1] --metric "Network In" --interval PT1H

Drag options to blanks, or click blank then click option'

A/subscriptions/abc/resourceGroups/rg1/providers/Microsoft.Sql/servers/sql1

B/subscriptions/abc/resourceGroups/rg1/providers/Microsoft.Compute/virtualMachines/vm1

C/subscriptions/abc/resourceGroups/rg1/providers/Microsoft.Storage/storageAccounts/sa1

D/subscriptions/abc/resourceGroups/rg1/providers/Microsoft.Network/networkInterfaces/nic1

Attempts:

3 left

💡 Hint

Common Mistakes

Using VM or storage account resource IDs for network metrics

Not specifying the correct resource type for the metric

The NetworkIn metric applies to network interfaces, so the resource must be a network interface ID.

3fill in blank

hard

Fix the error in the Azure CLI command to list metrics for a storage account.

Azure

az monitor metrics list --resource [1] --metric Transactions

Drag options to blanks, or click blank then click option'

A/subscriptions/xyz/resourceGroups/rg2/providers/Microsoft.Storage/storageAccounts/myStorage

B/subscriptions/xyz/resourceGroups/rg2/providers/Microsoft.Compute/virtualMachines/myVM

C/subscriptions/xyz/resourceGroups/rg2/providers/Microsoft.Network/networkInterfaces/myNIC

D/subscriptions/xyz/resourceGroups/rg2/providers/Microsoft.Sql/servers/mySqlServer

Attempts:

3 left

💡 Hint

Common Mistakes

Using VM or network interface resource IDs for storage metrics

Using SQL server resource ID for storage metrics

The Transactions metric is valid for storage accounts, so the resource must be a storage account ID.

4fill in blank

hard

Fill both blanks to create a query that lists CPU and Memory metrics for a VM in the last 30 minutes.

Azure

az monitor metrics list --resource [1] --metric [2] --interval PT30M

Drag options to blanks, or click blank then click option'

A/subscriptions/1234/resourceGroups/rgVM/providers/Microsoft.Compute/virtualMachines/vm01

BDiskReadBytes

CPercentage CPU Available Memory Bytes

DPercentage CPU Network In

Attempts:

3 left

💡 Hint

Common Mistakes

Using incomplete resource IDs

Using incorrect metric names or unrelated metrics

The resource must be the VM's full resource ID, and the metrics must include CPU and memory metrics separated by spaces.

5fill in blank

hard

Fill all three blanks to create a command that retrieves average Disk Write Bytes metric for a VM over the last hour with aggregation.

Azure

az monitor metrics list --resource [1] --metric [2] --aggregation [3] --interval PT1H

Drag options to blanks, or click blank then click option'

A/subscriptions/5678/resourceGroups/rgDisk/providers/Microsoft.Compute/virtualMachines/vmDisk01

BDisk Write Bytes

CAverage

DTotal

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect metric names

Using aggregation types not supported or unrelated to the metric

The command requires the VM's full resource ID, the correct metric name, and the aggregation type 'Average' to get average values.

Practice

1. What is the main purpose of metrics in Azure resource performance monitoring?

easy

A. To create new Azure resources automatically

B. To change resource configurations

C. To delete unused resources

D. To track how well resources are working over time

Solution

1. Step 1: Understand what metrics represent

   Metrics provide data about resource usage and performance over time.

2. Step 2: Identify the purpose of monitoring metrics

   Monitoring helps keep resources healthy and plan for future needs.

3. Final Answer:

   To track how well resources are working over time -> Option D

4. Quick Check:

   Metrics = Performance tracking [OK]

Hint: Metrics measure performance, not resource creation or deletion [OK]

Common Mistakes:

• Confusing metrics with resource management actions
• Thinking metrics change resource settings
• Assuming metrics create or delete resources

2. Which Azure CLI command correctly lists metrics for a resource?

easy

A. az metrics get --resource-group

B. az resource metrics show --name

C. az monitor metrics list --resource

D. az monitor resource metrics fetch --id

Solution

1. Step 1: Recall the correct Azure CLI syntax for metrics

   The official command to list metrics is az monitor metrics list with the resource specified.

2. Step 2: Verify the options

   Only az monitor metrics list --resource uses the correct command and parameter format.

3. Final Answer:

   az monitor metrics list --resource <resource-id> -> Option C

4. Quick Check:

   Correct CLI command = az monitor metrics list --resource [OK]

Hint: Use 'az monitor metrics list' to get metrics data [OK]

Common Mistakes:

• Using incorrect command verbs like 'get' or 'show'
• Mixing resource and resource-group parameters wrongly
• Adding unsupported flags or commands

3. Given this Azure CLI command output snippet for CPU percentage metric:

{"value": [{"timeseries": [{"data": [{"timeStamp": "2024-06-01T10:00:00Z", "average": 30.5}, {"timeStamp": "2024-06-01T10:05:00Z", "average": 45.2}]}]}]}

What is the average CPU usage at 10:05 AM?

medium

A. 45.2%

B. No data available

C. 75.7%

D. 30.5%

Solution

1. Step 1: Locate the timestamp 10:05 AM in the data

   Find the entry with "timeStamp": "2024-06-01T10:05:00Z".

2. Step 2: Read the average CPU value at that time

   The average value is 45.2% at 10:05 AM.

3. Final Answer:

   45.2% -> Option A

4. Quick Check:

   CPU at 10:05 = 45.2% [OK]

Hint: Match timestamp exactly to find correct metric value [OK]

Common Mistakes:

• Picking the wrong timestamp value
• Adding values instead of reading single entry
• Confusing average with total or max

4. You run az monitor metrics list --resource <id> but get an error: "Resource not found". What is the most likely cause?

medium

A. Metrics are not enabled for the resource

B. The resource ID is incorrect or does not exist

C. You forgot to login to Azure CLI

D. The command syntax is wrong

Solution

1. Step 1: Understand the error message

   "Resource not found" means Azure cannot locate the resource by the given ID.

2. Step 2: Identify common causes

   An incorrect or non-existent resource ID is the most common reason for this error.

3. Final Answer:

   The resource ID is incorrect or does not exist -> Option B

4. Quick Check:

   Resource not found = Wrong ID [OK]

Hint: Check resource ID spelling and existence first [OK]

Common Mistakes:

• Assuming metrics must be enabled to avoid this error
• Ignoring login status
• Blaming command syntax without checking resource ID

5. You want to monitor the average disk read bytes for a virtual machine over the last 24 hours using Azure CLI. Which command correctly achieves this?

hard

A. az monitor metrics list --resource --metric DiskReadBytes --interval PT24H --aggregation Average

B. az monitor metrics list --resource --metric DiskReadBytes --interval 24h --aggregation Total

C. az monitor metrics show --resource --metric DiskReadBytes --time-range 24h --aggregation Average

D. az metrics list --resource --metric DiskReadBytes --interval PT24H --aggregation Average

Solution

1. Step 1: Identify the correct command and parameters

   The command to list metrics is az monitor metrics list. The metric name is DiskReadBytes. The interval uses ISO 8601 duration format (PT24H for 24 hours). Aggregation for average is 'Average'.

2. Step 2: Compare options for correctness

   az monitor metrics list --resource --metric DiskReadBytes --interval PT24H --aggregation Average uses correct command, metric, interval format, and aggregation. Others have wrong commands, interval formats, or aggregation types.

3. Final Answer:

   az monitor metrics list --resource <vm-resource-id> --metric DiskReadBytes --interval PT24H --aggregation Average -> Option A

4. Quick Check:

   Correct CLI + metric + interval + aggregation = az monitor metrics list --resource --metric DiskReadBytes --interval PT24H --aggregation Average [OK]

Hint: Use ISO 8601 interval format and 'Average' aggregation [OK]

Common Mistakes:

• Using wrong command like 'az metrics show'
• Using incorrect interval format like '24h'
• Choosing 'Total' instead of 'Average' aggregation