Skip to content

Commit cad2bb7

Browse files
authored
Merge pull request #122063 from azarboon/patch-14
Update monitor-virtual-machine-alerts.md
2 parents d773712 + bb8d7dc commit cad2bb7

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-monitor/vm/monitor-virtual-machine-alerts.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,9 +95,11 @@ The following section lists common alert rules for virtual machines in Azure Mon
9595
> [!NOTE]
9696
> The details for log search alerts provided here are using data collected by using [VM Insights](vminsights-overview.md), which provides a set of common performance counters for the client operating system. This name is independent of the operating system type.
9797
98-
### Machine unavailable
98+
### Machine availability
9999
One of the most common monitoring requirements for a virtual machine is to create an alert if it stops running. The best method is to create a metric alert rule in Azure Monitor by using the VM availability metric, which is currently in public preview. For a walk-through on this metric, see [Create availability alert rule for Azure virtual machine](tutorial-monitor-vm-alert-availability.md).
100100

101+
An alert rule is limited to one activity log signal. So for every condition, one alert rule must be created. For example, "starts or stops the virtual machine" requires two alert rules. However, to be alerted when VM is restarted, only one alert rule is needed.
102+
101103
As described in [Scaling alert rules](#scaling-alert-rules), create an availability alert rule by using a subscription or resource group as the target resource. The rule applies to multiple virtual machines, including new machines that you create after the alert rule.
102104

103105
### Agent heartbeat

0 commit comments

Comments
 (0)