Alerts and action groups in Azure - Step-by-Step Execution

Process Flow - Alerts and action groups

Metric or Log Monitored

↓

Alert Rule Evaluates Condition

↓

Trigger Alert

↓

Action Group Executes

↓

Notification or Automation

The system monitors metrics or logs, evaluates alert rules, triggers alerts if conditions are met, and executes action groups to notify or automate responses.

Execution Sample

Azure

Monitor CPU > 80%
If true, trigger alert
Alert calls action group
Action group sends email

This setup watches CPU usage, triggers an alert if it goes above 80%, and sends an email via the action group.

Process Table

Step	Metric Value	Condition (CPU > 80%)	Alert Triggered	Action Group Executed	Notification Sent
1	65%	False	No	No	No
2	82%	True	Yes	Yes	Yes
3	78%	False	No	No	No
4	85%	True	Yes	Yes	Yes
5	70%	False	No	No	No

💡 Monitoring continues; alerts trigger only when CPU > 80% condition is true.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5
CPU Usage	N/A	65%	82%	78%	85%	70%
Alert Triggered	False	False	True	False	True	False
Action Group Executed	False	False	True	False	True	False
Notification Sent	False	False	True	False	True	False

Key Moments - 3 Insights

Why doesn't the alert trigger when CPU usage is 65%?

Because the condition CPU > 80% is false at 65%, so no alert is triggered as shown in execution_table step 1.

Does the action group run if the alert condition is false?

No, the action group only runs when the alert triggers, which happens only if the condition is true, as seen in steps 2 and 4.

What happens if the CPU usage fluctuates above and below 80%?

Alerts trigger each time the condition becomes true, and action groups execute accordingly, shown in steps 2 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the alert first triggered?

A Step 2

B Step 1

C Step 3

D Step 5

💡 Hint

Check the 'Alert Triggered' column in execution_table rows.

According to variable_tracker, what is the CPU usage at step 4?

A 78%

B 70%

C 85%

D 65%

💡 Hint

Look at the 'CPU Usage' row under 'After 4' column in variable_tracker.

If the alert condition changed to CPU > 75%, how would the alert trigger at step 3 change?

A Alert would not trigger at step 3

B Alert would trigger at step 3

C Action group would execute at step 1

D Notification would be sent at step 5

💡 Hint

Compare CPU usage at step 3 with new condition in execution_table and variable_tracker.

Concept Snapshot

Alerts watch metrics or logs.
If condition is true, alert triggers.
Alert calls action group.
Action group sends notifications or runs automation.
Alerts only trigger when conditions are met.

Full Transcript

In Azure, alerts monitor metrics or logs continuously. When a condition like CPU usage above 80% is met, the alert triggers. This triggers an action group, which can send notifications like emails or run automated tasks. If the condition is not met, no alert or action occurs. This flow repeats as metrics update over time.

Practice

1. What is the main purpose of an alert in Azure Monitor?

easy

A. To create virtual machines automatically

B. To notify you when a specific condition occurs in your cloud resources

C. To store data backups securely

D. To manage user permissions in Azure

Solution

1. Step 1: Understand what alerts monitor

   Alerts watch cloud resources and trigger when certain conditions happen, like high CPU or errors.

2. Step 2: Identify alert purpose

   The main goal is to notify you so you can act quickly and keep systems healthy.

3. Final Answer:

   To notify you when a specific condition occurs in your cloud resources -> Option B

4. Quick Check:

   Alerts = Notifications on conditions [OK]

Hint: Alerts notify on issues; think 'watch and warn' [OK]

Common Mistakes:

• Confusing alerts with resource creation
• Thinking alerts manage backups
• Assuming alerts control user access

2. Which of the following is the correct way to associate an action group with an alert rule in Azure?

easy

A. Create a new virtual network with the action group name

B. Add the action group as a tag to the resource

C. Specify the action group ID in the alert rule's actions section

D. Assign the action group to the resource's access control list

Solution

1. Step 1: Review alert rule configuration

   Alert rules include an actions section where you specify which action groups to notify or trigger.

2. Step 2: Confirm correct association method

   You link an action group by referencing its ID in the alert rule's actions, not by tags or network settings.

3. Final Answer:

   Specify the action group ID in the alert rule's actions section -> Option C

4. Quick Check:

   Action group linked via alert actions [OK]

Hint: Action groups go in alert actions, not tags or ACLs [OK]

Common Mistakes:

• Trying to add action groups as resource tags
• Confusing network setup with alert actions
• Assigning action groups to access control lists

3. Given this alert rule JSON snippet, what action group will be triggered when the alert fires?

{
  "name": "HighCPUAlert",
  "criteria": {"metricName": "Percentage CPU", "threshold": 80},
  "actions": [{"actionGroupId": "/subscriptions/123/resourceGroups/rg1/providers/microsoft.insights/actionGroups/NotifyTeam"}]
}

medium

A. NotifyTeam

B. BackupGroup

C. ScaleUpGroup

D. SecurityAlertGroup

Solution

1. Step 1: Locate action group ID in alert JSON

   The actions array contains an actionGroupId ending with 'NotifyTeam'.

2. Step 2: Match action group name

   The ID clearly points to the 'NotifyTeam' action group, so this group triggers on alert.

3. Final Answer:

   NotifyTeam -> Option A

4. Quick Check:

   ActionGroupId ends with NotifyTeam [OK]

Hint: Look for actionGroupId value in alert JSON [OK]

Common Mistakes:

• Picking wrong action group from unrelated names
• Ignoring the actionGroupId field
• Assuming default action group triggers

4. You created an alert rule but no notifications are sent when the condition is met. What is the most likely cause?

medium

A. The alert rule does not have any action groups assigned

B. The resource is offline

C. The alert rule threshold is set too low

D. The action group is disabled in Azure Security Center

Solution

1. Step 1: Check alert rule configuration

   If no notifications are sent, first verify if the alert rule has action groups assigned to send alerts.

2. Step 2: Understand action group role

   Action groups define who and how notifications are sent; without them, alerts trigger but no actions occur.

3. Final Answer:

   The alert rule does not have any action groups assigned -> Option A

4. Quick Check:

   No action groups = no notifications [OK]

Hint: Alerts need action groups to send notifications [OK]

Common Mistakes:

• Assuming resource offline stops alerts
• Thinking threshold affects notification sending
• Confusing action group status with Security Center

5. You want to create an alert that sends an email and triggers an Azure Function when CPU usage exceeds 90%. Which setup correctly achieves this?

hard

A. Create an alert rule with a metric condition for CPU > 90%, and assign an action group with only Azure Function action

B. Create an alert rule with a log query for CPU > 90%, and assign an action group with only email action

C. Create an alert rule with a metric condition for CPU > 90%, but no action group is needed if you have an Azure Function

D. Create an alert rule with a metric condition for CPU > 90%, and assign an action group with email and Azure Function actions

Solution

1. Step 1: Define alert condition and actions

   The alert must watch CPU metric > 90%, so use a metric condition. To notify and trigger automation, use an action group with both email and Azure Function actions.

2. Step 2: Confirm action group capabilities

   Action groups can include multiple actions like email and Azure Functions, enabling combined notifications and automation.

3. Final Answer:

   Create an alert rule with a metric condition for CPU > 90%, and assign an action group with email and Azure Function actions -> Option D

4. Quick Check:

   Metric alert + action group with email & function [OK]

Hint: Use action group with all needed actions for alert [OK]

Common Mistakes:

• Omitting action group when automation is needed
• Using log query instead of metric for CPU
• Assigning incomplete actions in action group