Metrics for resource performance in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are metrics in Azure Monitor?

Metrics are numerical values that describe the performance or health of an Azure resource over time. They help you understand how your resources are working.

beginner

Name two common types of metrics collected for Azure resources.

1. CPU usage - shows how much processing power is used.
2. Memory usage - shows how much memory is consumed.

beginner

Why is monitoring metrics important for cloud resources?

Monitoring metrics helps detect problems early, optimize resource use, and keep applications running smoothly without surprises.

beginner

How can you view metrics for an Azure resource?

You can view metrics in the Azure Portal under the resource's 'Metrics' section, or use Azure Monitor to create charts and alerts.

beginner

What is an alert in the context of Azure metrics?

An alert is a notification triggered when a metric crosses a set threshold, helping you respond quickly to issues.

Which of the following is a metric you might monitor for an Azure Virtual Machine?

A Number of users logged in

B CPU usage

C Website traffic

D Email count

CPU usage is a common performance metric for virtual machines.

Where can you find metrics for an Azure resource?

A Azure Active Directory

B Azure Marketplace

C Azure DevOps Pipelines

D Azure Portal under the resource's Metrics tab

Metrics are available in the Azure Portal under each resource's Metrics section.

What does an alert do in Azure Monitor?

A Sends a notification when a metric exceeds a threshold

B Automatically fixes resource issues

C Deletes unused resources

D Creates new resources

Alerts notify you when metrics cross thresholds so you can take action.

Which metric would best indicate if a web app is running slowly?

A Disk size

B CPU usage

C Response time

D Number of users

Response time shows how long the app takes to respond, indicating speed.

Why should you monitor memory usage of a cloud resource?

A To ensure it does not run out of memory and crash

B To increase the number of users

C To reduce internet speed

D To change the resource location

Monitoring memory helps prevent crashes due to running out of memory.

Explain what metrics are and why they are important for monitoring Azure resources.

Think about how numbers can tell you if something is working well or not.

Describe how you would use Azure Portal to check the performance of a virtual machine.

Imagine you are checking the health of a car by looking at its dashboard.

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