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/key-vault/general/alert.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,15 +51,15 @@ This document will cover the following topics:
51
51
3. Select **Metrics** under **Monitoring**
52
52
53
53
> [!div class="mx-imgBorder"]
54
-
> 
54
+
> 
55
55
56
56
4. Update the title of the chart to what you want to see on your dashboard.
57
57
5. Select the scope. In this example we will select a single key vault.
58
58
6. Select the Metric **Overall Vault Availability** and Aggregation **Avg**
59
59
7. Update the time range to the Last 24 Hours and update the time granularity to 1 minute.
60
60
61
61
> [!div class="mx-imgBorder"]
62
-
> 
62
+
> 
63
63
64
64
8. Repeat the steps above for the Vault Saturation and Service API Latency metrics. Select **Pin to Dashboard** to save your metrics into a dashboard.
65
65
@@ -69,19 +69,19 @@ This document will cover the following topics:
69
69
9. To monitor all of the types of operations on the key vault, use the **Total Service API Hits** Metric, and Select **Apply Splitting by Activity Type**
70
70
71
71
> [!div class="mx-imgBorder"]
72
-
> 
72
+
> 
73
73
74
74
10. To monitor for error codes on the key vault, use the **Total Service API Results** Metric, and Select **Apply Splitting by Activity Type**
75
75
76
76
> [!div class="mx-imgBorder"]
77
-
> 
77
+
> 
78
78
79
79
Now you will have a dashboard that looks like this. You can click the 3 dots on the top right of each tile and you can rearrange and resize the tiles as you need.
80
80
81
81
Once you save and publish the dashboard, it will create a new resource in your Azure subscription. You will be able to see it at anytime by searching for "shared dashboard".
82
82
83
83
> [!div class="mx-imgBorder"]
84
-
> 
84
+
> 
85
85
86
86
## How to configure alerts on your Key Vault
87
87
@@ -99,20 +99,20 @@ An action group is a configurable list of notifications and properties.
99
99
3. Select **Manage Actions**
100
100
101
101
> [!div class="mx-imgBorder"]
102
-
> 
102
+
> 
103
103
104
104
4. Select **+ Add Action Group**
105
105
106
106
> [!div class="mx-imgBorder"]
107
-
> 
107
+
> 
108
108
109
109
5. Choose the **Action Type** for your Action Group. In this example, we will create an email alert.
110
110
111
111
> [!div class="mx-imgBorder"]
112
-
> 
112
+
> 
113
113
114
114
> [!div class="mx-imgBorder"]
115
-
> 
115
+
> 
116
116
117
117
6. Click **OK** at the bottom of the page. You have successfully created an action group.
118
118
@@ -123,20 +123,20 @@ Now that you have configured an action group, we will configure the the key vaul
123
123
1. Select your key vault resource in the Azure portal and select **Alerts** under **Monitoring**
124
124
125
125
> [!div class="mx-imgBorder"]
126
-
> 
126
+
> 
127
127
128
128
2. Select **New Alert Rule**
129
129
130
130
> [!div class="mx-imgBorder"]
131
-
> 
131
+
> 
132
132
133
133
3. Select the scope of your alert rule. You can select a single vault or multiple.
134
134
135
135
> [!IMPORTANT]
136
136
> Please note that when you are selecting multiple vaults for the scope of your alerts, all selected vaults must be in the same region. You will have to configure separate alert rules for vaults in different regions.
137
137
138
138
> [!div class="mx-imgBorder"]
139
-
> 
139
+
> 
140
140
141
141
4. Select the conditions for your alerts. You can choose any of the following signals and define your logic for alerting. The Key Vault team recommends configuring the following alerting thresholds.
142
142
@@ -147,13 +147,13 @@ Now that you have configured an action group, we will configure the the key vaul
147
147
+ Total Error Codes higher than average (Dynamic Threshold)
148
148
149
149
> [!div class="mx-imgBorder"]
150
-
> 
150
+
> 
151
151
152
152
### Example 1: Configuring a static alert threshold for latency
153
153
154
154
Select **Overall Service API Latency** as the signal name
155
155
> [!div class="mx-imgBorder"]
156
-
> 
156
+
> 
157
157
158
158
Please see the following configuration parameters.
159
159
@@ -166,14 +166,14 @@ Please see the following configuration parameters.
166
166
+ Select **Done**
167
167
168
168
> [!div class="mx-imgBorder"]
169
-
> 
169
+
> 
170
170
171
171
### Example 2: Configuring a dynamic alert threshold for vault saturation
172
172
173
173
When you use a dynamic alert, you will be able to see historical data of the key vault you have selected. The blue area represents the average usage of your key vault. The red area shows spikes that would have triggered an alert provided other criteria in the alert configuration are met. The red dots show instances of violations where the criteria for the alert was met during the aggregated time window. You can set an alert to fire after a certain number of violations within a set time. If you don't want to include past data, there is an option to exclude old data below in advanced settings.
174
174
175
175
> [!div class="mx-imgBorder"]
176
-
> 
176
+
> 
177
177
178
178
Please see the following configuration parameters.
179
179
@@ -187,17 +187,17 @@ Please see the following configuration parameters.
187
187
+ Select **Done**
188
188
189
189
> [!div class="mx-imgBorder"]
190
-
> 
190
+
> 
191
191
192
192
5. Add the action group that you have configured
193
193
194
194
> [!div class="mx-imgBorder"]
195
-
> 
195
+
> 
196
196
197
197
6. Enable the alert and assign a severity
198
198
199
199
> [!div class="mx-imgBorder"]
200
-
> 
200
+
> 
201
201
202
202
7. Create the alert
203
203
@@ -207,4 +207,4 @@ Once you have followed all of the steps above, you should receive email alerts w
207
207
### Example email alert
208
208
209
209
> [!div class="mx-imgBorder"]
210
-
> 
210
+
> 
0 commit comments