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-multiple-time-series-single-rule.md
+37-37Lines changed: 37 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,14 +30,14 @@ An alert rule monitors a single time series when it meets all the following cond
30
30
31
31
An example of such an alert rule, with only the relevant properties shown:
32
32
33
-
-**Target resource**: *myVM1*
34
-
-**Metric**: *Percentage CPU*
33
+
-**Target resource**: *VM-a*
34
+
-**Signal**: *Percentage CPU*
35
35
-**Operator**: *Greater Than*
36
-
-**Threshold**: *70*
36
+
-**Threshold**: *80*
37
37
38
38
For this alert rule, a single metric time series is monitored:
39
39
40
-
- Percentage CPU where *Resource*=’myVM1’ > 70%
40
+
- Percentage CPU where *Resource*=’VM-a’ > 80%
41
41
42
42
43
43
@@ -55,26 +55,26 @@ A single metric alert rule can monitor multiple resources, provided the resource
55
55
56
56
An example of such an alert rule:
57
57
58
-
-**Target resource**: *myVM1, myVM2*
59
-
-**Metric**: *Percentage CPU*
58
+
-**Target resource**: *VM-a, myVM2*
59
+
-**Signal**: *Percentage CPU*
60
60
-**Operator**: *Greater Than*
61
-
-**Threshold**: *70*
61
+
-**Threshold**: *80*
62
62
63
63
For this alert rule, two metric time series are monitored separately:
64
64
65
-
- Percentage CPU where *Resource*=’myVM1’ > 70%
66
-
- Percentage CPU where *Resource*=’myVM2’ > 70%
65
+
- Percentage CPU where *Resource*=’VM-a’ > 80%
66
+
- Percentage CPU where *Resource*=’myVM2’ > 80%
67
67
68
68
69
69
70
70
In a multi-resource alert rule, the condition is evaluated separately for each of the resources (or more accurately, for each of the metric time series corresponded to each resource). As a result, alerts are also fired for each resource separately.
71
71
72
-
For example, assume we've set the preceding alert rule to monitor for CPU above 70%. In the evaluated time period, that is, the last 5 minutes:
72
+
For example, assume we've set the preceding alert rule to monitor for CPU above 80%. In the evaluated time period, that is, the last 5 minutes:
73
73
74
-
- The *Percentage CPU* of *myVM1* is greater than 70%.
74
+
- The *Percentage CPU* of *VM-a* is greater than 80%.
75
75
- The *Percentage CPU* of *myVM2* is at 50%.
76
76
77
-
The alert rule triggers on *myVM1* but not *myVM2*. These triggered alerts are independent. They can also resolve at different times depending on the individual behavior of each of the virtual machines.
77
+
The alert rule triggers on *VM-a* but not *VM-b*. These triggered alerts are independent. They can also resolve at different times depending on the individual behavior of each of the virtual machines.
78
78
79
79
For more information about multi-resource alert rules and the resource types supported for this capability, see [Monitoring at scale using metric alerts in Azure Monitor](alerts-types.md#monitor-multiple-resources).
80
80
@@ -87,20 +87,20 @@ A single metric alert rule can also monitor up to five conditions per alert rule
87
87
88
88
For example:
89
89
90
-
-**Target resource**: *myVM1*
90
+
-**Target resource**: *VM-a*
91
91
- Condition1
92
-
-**Metric**: *Percentage CPU*
92
+
-**Signa**: *Percentage CPU*
93
93
-**Operator**: *Greater Than*
94
-
-**Threshold**: *70*
94
+
-**Threshold**: *80*
95
95
- Condition2
96
-
-**Metric**: *Network In Total*
96
+
-**Signal**: *Network In Total*
97
97
-**Operator**: *Greater Than*
98
98
-**Threshold**: *20 MB*
99
99
100
100
For this alert rule, two metric time series are being monitored:
101
101
102
-
- The *Percentage CPU* where *Resource*=’myVM1’ > 70%.
103
-
- The *Network In Total* where *Resource*=’myVM1’ > 20 MB.
102
+
- The *Percentage CPU* where *Resource*=’VM-a’ > 80%.
103
+
- The *Network In Total* where *Resource*=’VM-a’ > 20 MB.
104
104
105
105
106
106
@@ -117,18 +117,18 @@ For example, you can choose to have an alert fired when the number of transactio
117
117
118
118
An example of an alert rule monitoring multiple dimensions is:
119
119
120
-
-**Target resource**: *myStorage1*
121
-
-**Metric**: *Transactions*
120
+
-**Target resource**: *mystorage1*
121
+
-**Signal**: *Transactions*
122
122
-**Dimensions**:
123
-
* API name = *GetBlob, DeleteBlob, PutPage*
123
+
* API name = *EntityGroupTransaction, GetBlob, PutPage*
124
124
-**Operator**: *Greater Than*
125
-
-**Threshold**: *70*
125
+
-**Threshold**: *80*
126
126
127
127
For this alert rule, three metric time series are being monitored:
128
128
129
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’GetBlob’ > 70
130
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’DeleteBlob’ > 70
131
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’PutPage’ > 70
129
+
- Transactions where *Resource*=’mystorage1’ and *API Name*=’EntityGroupTransaction’ > 80
130
+
- Transactions where *Resource*=’mystorage1’ and *API Name*=’GetBlob’ > 80
131
+
- Transactions where *Resource*=’mystorage1’ and *API Name*=’PutPage’ > 80
132
132
133
133
134
134
@@ -137,30 +137,30 @@ A multi-dimension metric alert rule can also monitor multiple dimension values f
137
137
An example of this type of alert rule:
138
138
139
139
-**Target resource**: *myStorage1*
140
-
-**Metric**: *Transactions*
140
+
-**Signal**: *Transactions*
141
141
-**Dimensions**:
142
142
* API name = *GetBlob, DeleteBlob, PutPage*
143
143
* Authentication = *SAS, AccountKey*
144
144
-**Operator**: *Greater Than*
145
-
-**Threshold**: *70*
145
+
-**Threshold**: *80*
146
146
147
147
For this alert rule, six metric time series are being monitored separately:
148
148
149
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’GetBlob’ and *Authentication*=’SAS’ > 70
150
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’GetBlob’ and *Authentication*=’AccountKey’ > 70
151
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’DeleteBlob’ and *Authentication*=’SAS’ > 70
152
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’DeleteBlob’ and *Authentication*=’AccountKey’ > 70
153
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’PutPage’ and *Authentication*=’SAS’ > 70
154
-
- Transactions where *Resource*=’myStorage1’ and *API Name*=’PutPage’ and *Authentication*=’AccountKey’ > 70
149
+
- Transactions where *Resource*=’myStorage1’ and *API Name*=’GetBlob’ and *Authentication*=’SAS’ > 80
150
+
- Transactions where *Resource*=’myStorage1’ and *API Name*=’GetBlob’ and *Authentication*=’AccountKey’ > 80
151
+
- Transactions where *Resource*=’myStorage1’ and *API Name*=’DeleteBlob’ and *Authentication*=’SAS’ > 80
152
+
- Transactions where *Resource*=’myStorage1’ and *API Name*=’DeleteBlob’ and *Authentication*=’AccountKey’ > 80
153
+
- Transactions where *Resource*=’myStorage1’ and *API Name*=’PutPage’ and *Authentication*=’SAS’ > 80
154
+
- Transactions where *Resource*=’myStorage1’ and *API Name*=’PutPage’ and *Authentication*=’AccountKey’ > 80
155
155
156
156
157
157
158
158
### Advanced multi-dimension features
159
159
160
-
-**Select all current and future dimensions**: You can choose to monitor all possible values of a dimension, including future values. Such an alert rule will scale automatically to monitor all values of the dimension without you needing to modify the alert rule every time a dimension value is added or removed.
161
-
-**Exclude dimensions**: Selecting the **≠** (exclude) operator for a dimension value is equivalent to selecting all other values of that dimension, including future values.
162
-
-**Add new and custom dimensions**: The dimension values displayed in the Azure portal are based on metric data collected in the last day. If the dimension value you're looking for isn't yet emitted, you can add a custom dimension value.
163
-
-**Match dimensions with a prefix**: You can choose to monitor all dimension values that start with a specific pattern by selecting the **Starts with** operator and entering a custom prefix.
160
+
1.**Select all current and future dimensions**: You can choose to monitor all possible values of a dimension, including future values. Such an alert rule will scale automatically to monitor all values of the dimension without you needing to modify the alert rule every time a dimension value is added or removed.
161
+
1.**Exclude dimensions**: Selecting the **≠** (exclude) operator for a dimension value is equivalent to selecting all other values of that dimension, including future values.
162
+
1.**Add new and custom dimensions**: The dimension values displayed in the Azure portal are based on metric data collected in the last day. If the dimension value you're looking for isn't yet emitted, you can add a custom dimension value.
163
+
1.**Match dimensions with a prefix**: You can choose to monitor all dimension values that start with a specific pattern by selecting the **Starts with** operator and entering a custom prefix.
164
164
165
165
0 commit comments