You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/platform/alerts-metric-overview.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,18 +118,20 @@ Increasing look-back periods and number of violations can also allow filtering a
118
118
119
119
## Monitoring at scale using metric alerts in Azure Monitor
120
120
121
-
So far, you have seen how a single metric alert could be used to monitor one or many metric time-series related to a single Azure resource. Many times, you might want the same alert rule applied to many resources. Azure Monitor also supports monitoring multiple resources (of the same type) with one metric alert rule, for resources that exist in the same Azure region. This feature is currently supported for these services:
121
+
So far, you have seen how a single metric alert could be used to monitor one or many metric time-series related to a single Azure resource. Many times, you might want the same alert rule applied to many resources. Azure Monitor also supports monitoring multiple resources (of the same type) with one metric alert rule, for resources that exist in the same Azure region.
122
122
123
-
- SQL server databases
124
-
- SQL server elastic pools
125
-
- Data box edge devices
126
-
- Virtual machines (public cloud only)
123
+
This feature is currently supported for platform metrics (not custom metrics) for the following services in the following Azure clouds:
127
124
128
-
Also, this feature is only available for platform metrics, and isn't supported for custom metrics.
125
+
| Service | Public Azure | Government | China |
126
+
|:--------|:--------|:--------|:--------|
127
+
| Virtual machines |**Yes**| No | No |
128
+
| SQL server databases |**Yes**|**Yes**| No |
129
+
| SQL server elastic pools |**Yes**|**Yes**| No |
130
+
| Data box edge devices |**Yes**|**Yes**| No |
129
131
130
-
You can specify the scope of monitoring by a single metric alert rule in one of three ways:
132
+
You can specify the scope of monitoring by a single metric alert rule in one of three ways. For example, with virtual machines you can specify the scope as:
131
133
132
-
-as a list of virtual machines in one Azure region within a subscription
134
+
- a list of virtual machines in one Azure region within a subscription
133
135
- all virtual machines (in one Azure region) in one or more resource groups in a subscription
134
136
- all virtual machines (in one Azure region) in one subscription
0 commit comments