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/alerts/alerts-metric-create-templates.md
+34-34Lines changed: 34 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.reviewer: harelbr
16
16
This article shows how you can use an [Azure Resource Manager template (ARM template)](../../azure-resource-manager/templates/syntax.md) to configure [newer metric alerts](./alerts-metric-near-real-time.md) in Azure Monitor. You can use ARM templates to programmatically set up alerts in a consistent and reproducible way across your environments. Newer metric alerts are currently available in [this set of resource types](./alerts-metric-near-real-time.md#metrics-and-dimensions-supported).
17
17
18
18
> [!IMPORTANT]
19
-
> The resource template for creating metric alerts for resource type Azure Log Analytics workspace, that is, `Microsoft.OperationalInsights/workspaces`, requires more steps. For more information, see [Metric Alerts for Logs - Resource template](./alerts-metric-logs.md#resource-template-for-metric-alerts-for-logs).
19
+
> The resource template for creating metric alerts for resource type Azure Log Analytics workspace (that is, `Microsoft.OperationalInsights/workspaces`) requires more steps. For more information, see [Metric Alerts for Logs - Resource template](./alerts-metric-logs.md#resource-template-for-metric-alerts-for-logs).
20
20
21
21
The basic steps are:
22
22
@@ -198,7 +198,7 @@ Save the following JSON script as *simplestaticmetricalert.json* for this walkth
198
198
}
199
199
```
200
200
201
-
An explanation of the schema and properties for an alert rule [is available here](/rest/api/monitor/metricalerts/createorupdate).
201
+
An explanation of the schema and properties for an alert rule is available [in this article](/rest/api/monitor/metricalerts/createorupdate).
202
202
203
203
You can set the values for the parameters either on the command line or through a parameter file. A sample parameter file is provided.
204
204
@@ -245,7 +245,7 @@ Save the following JSON script as *simplestaticmetricalert.parameters.json* and
245
245
246
246
You can create the metric alert using the template and parameters file by using PowerShell or the Azure CLI.
> While the metric alert could be created in a different resource group to the target resource, we recommend using the same resource group as your target resource.
273
+
> Although you can create the metric alert in a resource group that's different from the target resource, we recommend using the same resource group as your target resource.
274
274
275
275
## Template for a simple Dynamic Thresholds metric alert
276
276
@@ -470,7 +470,7 @@ Save the following JSON script as *simpledynamicmetricalert.json* for this walkt
470
470
}
471
471
```
472
472
473
-
An explanation of the schema and properties for an alert rule [is available here](/rest/api/monitor/metricalerts/createorupdate).
473
+
An explanation of the schema and properties for an alert rule is available [in this article](/rest/api/monitor/metricalerts/createorupdate).
474
474
475
475
You can set the values for the parameters either on the command line or through a parameter file. A sample parameter file is provided.
476
476
@@ -526,7 +526,7 @@ Save the following JSON script as *simpledynamicmetricalert.parameters.json* and
526
526
527
527
You can create the metric alert using the template and parameters file by using PowerShell or the Azure CLI.
@@ -551,19 +551,19 @@ az deployment group create \
551
551
552
552
> [!NOTE]
553
553
>
554
-
> While the metric alert could be created in a different resource group to the target resource, we recommend using the same resource group as your target resource.
554
+
> Although you can create the metric alert in a resource group that's different from the target resource, we recommend using the same resource group as your target resource.
555
555
556
556
## Template for a static threshold metric alert that monitors multiple criteria
557
557
558
-
Newer metric alerts support alerting on multi-dimensional metrics and support defining multiple criteria of up to five criterions per alert rule. You can use the following template to create a more advanced metric alert rule on dimensional metrics and specify multiple criteria.
558
+
Newer metric alerts support alerting on multi-dimensional metrics and support defining multiple criteria (up to five per alert rule). You can use the following template to create a more advanced metric alert rule on dimensional metrics and specify multiple criteria.
559
559
560
560
Note the following constraints when you use dimensions in an alert rule that contains multiple criteria:
561
561
562
562
- You can only select one value per dimension within each criterion.
563
563
- You can't use "\*" as a dimension value.
564
-
- When metrics that are configured in different criterions support the same dimension, a configured dimension value must be explicitly set in the same way for all those metrics in the relevant criterions:
564
+
- When metrics that are configured in different criteria support the same dimension, a configured dimension value must be explicitly set in the same way for all those metrics in the relevant criteria:
565
565
566
-
-In the following example, because both the **Transactions** and **SuccessE2ELatency** metrics have an **ApiName** dimension, and *criterion1* specifies the *"GetBlob"* value for the **ApiName** dimension, then *criterion2* must also set a *"GetBlob"* value for the **ApiName** dimension.
566
+
In the following example, because both the **Transactions** and **SuccessE2ELatency** metrics have an **ApiName** dimension, and *criterion1* specifies the *"GetBlob"* value for the **ApiName** dimension, then *criterion2* must also set a *"GetBlob"* value for the **ApiName** dimension.
567
567
568
568
Save the following JSON script as *advancedstaticmetricalert.json* for this walkthrough.
569
569
@@ -768,7 +768,7 @@ Save and modify the following JSON script as *advancedstaticmetricalert.paramete
768
768
769
769
You can create the metric alert using the template and parameters file by using PowerShell or the Azure CLI from your current working directory.
@@ -1807,7 +1807,7 @@ Save and modify the following JSON script as *all-vms-in-resource-group-static.p
1807
1807
1808
1808
You can create the static metric alert using the template and parameters file by using PowerShell or the Azure CLI from your current working directory.
0 commit comments