Skip to content

Commit 1def839

Browse files
committed
fixed up alerts
1 parent 3646370 commit 1def839

File tree

1 file changed

+14
-10
lines changed

1 file changed

+14
-10
lines changed

articles/azure-monitor/insights/vminsights-alerts.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -22,16 +22,16 @@ There are two types of log alerts in Azure Monitor:
2222
- [Metric measurement alerts](../platform/alerts-unified-log.md#metric-measurement-alert-rules) create a separate alert for each record in a query that has a value that exceeds a threshold defined in the alert rule. These alert rules are ideal for performance data collected by Azure Monitor for VMs since they can create individual alerts for each computer.
2323

2424

25-
## Alert rule details
26-
Since the target resource for log alert rules is always a Log Analytics workspace, the log query must include any filter for particular virtual machines or virtual machine scale sets. For metric measurement alert rules, summarize the query results by computer in order to evaluate each separately.
25+
## Alert rule walkthrough
26+
This section walks through the creation of a metric measurement alert rule using performance data from Azure Monitor for VMs. You can use this basic process with a variety of log queries to alert on different performance counters.
2727

28-
Start by creating a new alert rule following the procedure in [Create, view, and manage log alerts using Azure Monitor](../platform/alerts-log.md). For the **Resource**, select the Log Analytics workspace that Azure Monitor VMs uses in your subscription.
28+
Start by creating a new alert rule following the procedure in [Create, view, and manage log alerts using Azure Monitor](../platform/alerts-log.md). For the **Resource**, select the Log Analytics workspace that Azure Monitor VMs uses in your subscription. Since the target resource for log alert rules is always a Log Analytics workspace, the log query must include any filter for particular virtual machines or virtual machine scale sets.
2929

30-
For the **Condition** of the alert rule, provide one of the queries in the section below as the **Search query**. The query must return a numeric property called *AggregatedValue*. It should summarize the data by computer so that you can create a separate alert for each virtual machine that exceeds the threshold.
30+
For the **Condition** of the alert rule, use one of the queries in the [section below](#sample-alert-queries) as the **Search query**. The query must return a numeric property called *AggregatedValue*. It should summarize the data by computer so that you can create a separate alert for each virtual machine that exceeds the threshold.
3131

32-
In the **Alert logic**, select **Metric measurement** and then provide a **Threshold value**. In **Trigger Alert Based On**, specify how many times the threshold must be exceeded before an alert is created. For example, you probably don't care if the processor exceeds a threshold once and then returns to normal, but you do care if it continues to exceed the threshold over multiple measurements.
32+
In the **Alert logic**, select **Metric measurement** and then provide a **Threshold value**. In **Trigger Alert Based On**, specify how many times the threshold must be exceeded before an alert is created. For example, you probably don't care if the processor exceeds a threshold once and then returns to normal, but you do care if it continues to exceed the threshold over multiple consecutive measurements.
3333

34-
The **Evaluated based on** section defines how often the query is run and the time window for the query. In the example shown below, the query will run every 15 minutes and evalute performance collected over the previous 15 minutes.
34+
The **Evaluated based on** section defines how often the query is run and the time window for the query. In the example shown below, the query will run every 15 minutes and evalute performance values collected over the previous 15 minutes.
3535

3636

3737
![Metric measurement alert rule](media/vminsights-alerts/metric-measurement-alert.png)
@@ -145,7 +145,8 @@ InsightsMetrics
145145
| summarize AggregatedValue = avg(Val) by bin(TimeGenerated, 15m), Computer, _ResourceId, NetworkInterface
146146
```
147147

148-
## Virtual machine scale set
148+
### Virtual machine scale set
149+
Modify with your subscription ID, resource group, and VM scale set name.
149150

150151
```kusto
151152
InsightsMetrics
@@ -155,7 +156,8 @@ InsightsMetrics
155156
| summarize AggregatedValue = avg(Val) by bin(TimeGenerated, 15m), _ResourceId
156157
```
157158

158-
## Specific virtual machine
159+
### Specific virtual machine
160+
Modify with your subscription ID, resource group, and VM name.
159161

160162
```kusto
161163
InsightsMetrics
@@ -165,7 +167,8 @@ InsightsMetrics
165167
| summarize AggregatedValue = avg(Val) by bin(TimeGenerated, 15m)
166168
```
167169

168-
## CPU utilization for all compute resources in a subscription
170+
### CPU utilization for all compute resources in a subscription
171+
Modify with your subscription ID.
169172

170173
```kusto
171174
InsightsMetrics
@@ -175,7 +178,8 @@ InsightsMetrics
175178
| summarize AggregatedValue = avg(Val) by bin(TimeGenerated, 15m), _ResourceId
176179
```
177180

178-
## CPU utilization for all compute resources in a resource group
181+
### CPU utilization for all compute resources in a resource group
182+
Modify with your subscription ID and resource group.
179183

180184
```kusto
181185
InsightsMetrics

0 commit comments

Comments
 (0)