Skip to content

Commit 6c02c0f

Browse files
authored
Merge pull request #107956 from rboucher/patch-17
update for government support
2 parents 235e651 + a6edb7f commit 6c02c0f

File tree

1 file changed

+13
-4
lines changed

1 file changed

+13
-4
lines changed

articles/azure-monitor/platform/alerts-metric-overview.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Understand how metric alerts work in Azure Monitor.
33
description: Get an overview of what you can do with metric alerts and how they work in Azure Monitor.
4-
ms.date: 12/5/2019
4+
ms.date: 03/17/2020
55
ms.topic: conceptual
66
ms.subservice: alerts
77

@@ -118,11 +118,20 @@ Increasing look-back periods and number of violations can also allow filtering a
118118

119119
## Monitoring at scale using metric alerts in Azure Monitor
120120

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 only in Azure public cloud and only for virtual machines, SQL server databases, SQL server elastic pools and Data box edge devices. Also, this feature is only available for platform metrics, and isn't supported for custom metrics.
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.
122122

123-
You can specify the scope of monitoring by a single metric alert rule in one of three ways:
123+
This feature is currently supported for platform metrics (not custom metrics) for the following services in the following Azure clouds:
124124

125-
- as a list of virtual machines in one Azure region within a subscription
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 |
131+
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:
133+
134+
- a list of virtual machines in one Azure region within a subscription
126135
- all virtual machines (in one Azure region) in one or more resource groups in a subscription
127136
- all virtual machines (in one Azure region) in one subscription
128137

0 commit comments

Comments
 (0)