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/app/availability.md
+59-58Lines changed: 59 additions & 58 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,61 +77,10 @@ There are four types of availability tests:
77
77
78
78
| Setting | Description |
79
79
|--------|--------------|
80
-
|**Test timeout**|Decrease this value to be alerted about slow responses. The test is counted as a failure if the responses from your site haven't been received within this period. If you selected **Parse dependent requests**, all the images, style files, scripts, and other dependent resources must have been received within this period. |
80
+
|**Test timeout**|Decrease this value to be alerted about slow responses. The test is counted as a failure if the responses from your site haven't been received within this period. If you selected **Parse dependent requests**, all the images, style files, scripts, and other dependent resources must have been received within this period. |
81
81
|**HTTP response**| The returned status code that's counted as a success. The number 200 is the code that indicates that a normal webpage has been returned. |
82
82
|**Content match**| A string, like "Welcome!" We test that an exact case-sensitive match occurs in every response. It must be a plain string, without wildcards. Don't forget that if your page content changes, you might have to update it. *Only English characters are supported with content match.*|
83
83
84
-
### Alerts
85
-
86
-
| Setting | Description |
87
-
|---------|-------------|
88
-
|**Near real time**| We recommend using near real time alerts. Configuring this type of alert is done after your availability test is created. |
89
-
|**Alert location threshold**|We recommend a minimum of 3/5 locations. The optimal relationship between alert location threshold and the number of test locations is **alert location threshold** = **number of test locations - 2, with a minimum of five test locations.**|
90
-
91
-
### Location population tags
92
-
93
-
You can use the following population tags for the geo-location attribute when you deploy an availability URL ping test by using Azure Resource Manager.
| France South (Formerly France Central) | emea-ch-zrh-edge |
105
-
| France Central | emea-fr-pra-edge |
106
-
| Japan East | apac-jp-kaw-edge |
107
-
| North Europe | emea-gb-db3-azr |
108
-
| North Central US | us-il-ch1-azr |
109
-
| South Central US | us-tx-sn1-azr |
110
-
| Southeast Asia | apac-sg-sin-azr |
111
-
| UK West | emea-se-sto-edge |
112
-
| West Europe | emea-nl-ams-azr |
113
-
| West US | us-ca-sjc-azr |
114
-
| UK South | emea-ru-msa-edge |
115
-
116
-
#### Azure Government
117
-
118
-
| Display name | Population name |
119
-
|----------------|---------------------|
120
-
| USGov Virginia | usgov-va-azr |
121
-
| USGov Arizona | usgov-phx-azr |
122
-
| USGov Texas | usgov-tx-azr |
123
-
| USDoD East | usgov-ddeast-azr |
124
-
| USDoD Central | usgov-ddcentral-azr |
125
-
126
-
#### Microsoft Azure operated by 21Vianet
127
-
128
-
| Display name | Population name |
129
-
|----------------|---------------------|
130
-
| China East | mc-cne-azr |
131
-
| China East 2 | mc-cne2-azr |
132
-
| China North | mc-cnn-azr |
133
-
| China North 2 | mc-cnn2-azr |
134
-
135
84
## [TrackAvailability()](#tab/track)
136
85
137
86
> [!IMPORTANT]
@@ -157,18 +106,19 @@ You can use the following population tags for the geo-location attribute when yo
157
106
158
107
1. Create an Azure Functions resource.
159
108
160
-
If you already have an Application Insights resource:
109
+
***If you already have an Application Insights resource:**
161
110
162
-
*By default, Azure Functions creates an Application Insights resource. But if you want to use a resource you created previously, you must specify that during creation.
111
+
By default, Azure Functions creates an Application Insights resource. If you want to use a resource you created previously, you must specify that during creation.
163
112
164
-
* Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app) with the following modification:
113
+
Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app) with the following modification:
165
114
166
-
On the **Monitoring** tab, select the **Application Insights** dropdown box and then enter or select the name of your resource.
115
+
On the **Monitoring** tab, select the **Application Insights** dropdown box and then enter or select the name of your resource:
167
116
168
117
:::image type="content" source="media/availability-azure-functions/app-insights-resource.png" alt-text="Screenshot that shows selecting your existing Application Insights resource on the Monitoring tab.":::
169
118
170
-
* If you don't have an Application Insights resource created yet for your timer-triggered function:
171
-
* By default, when you're creating your Azure Functions application, it creates an Application Insights resource for you. Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app).
119
+
***If you don't have an Application Insights resource created yet for your timer-triggered function:**
120
+
121
+
By default, when you're creating your Azure Functions application, it creates an Application Insights resource for you. Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app).
172
122
173
123
> [!NOTE]
174
124
> You can host your functions on a Consumption, Premium, or App Service plan. If you're testing behind a virtual network or testing nonpublic endpoints, you'll need to use the Premium plan in place of the Consumption plan. Select your plan on the **Hosting** tab. Ensure the latest .NET version is selected when you create the function app.
@@ -339,8 +289,59 @@ public async static Task RunAvailabilityTestAsync(ILogger log)
339
289
340
290
---
341
291
292
+
293
+
342
294
## Availability alerts
343
295
296
+
| Setting | Description |
297
+
|---------|-------------|
298
+
|**Near real time**| We recommend using near real time alerts. Configuring this type of alert is done after your availability test is created. |
299
+
|**Alert location threshold**|We recommend a minimum of 3/5 locations. The optimal relationship between alert location threshold and the number of test locations is **alert location threshold** = **number of test locations - 2, with a minimum of five test locations.**|
300
+
301
+
### Location population tags
302
+
303
+
You can use the following population tags for the geo-location attribute when you deploy an availability URL ping test by using Azure Resource Manager.
0 commit comments