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
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ There are four types of availability tests:
87
87
88
88
### Basic code sample
89
89
90
-
This example is designed solely to show you the mechanics of how the `TrackAvailability()` API call works within an Azure Functions app. It doesn't show you how to write the underlying HTTP test code or business logic that's required to turn this example into a fully functional availability test.
90
+
This example is designed solely to show you the mechanics of how the `TrackAvailability()` API call works within an Azure Functions app. It doesn't show how to write the underlying HTTP test code or business logic required to turn this example into a fully functional availability test.
91
91
92
92
> [!NOTE]
93
93
> To follow these instructions, you must use either the [App Service](../../azure-functions/dedicated-plan.md) plan or Functions Premium plan to allow editing code in App Service Editor.
@@ -420,7 +420,7 @@ The following steps walk you through the process of creating [standard tests](av
420
420
421
421
#### Get started
422
422
423
-
1. Connect to your subscription with Azure PowerShell (Connect-AzAccount + Set-AzContext).
423
+
1. Connect to your subscription with Azure PowerShell (`Connect-AzAccount` + `Set-AzContext`).
424
424
425
425
1. List all URL ping tests in the current subscription:
426
426
@@ -430,9 +430,9 @@ The following steps walk you through the process of creating [standard tests](av
1. The new standard test doesn't have alert rules by default, so it doesn't create noisy alerts. No changes are made to your URL ping test so you can continue to rely on it for alerts.
468
+
The new standard test doesn't have alert rules by default, so it doesn't create noisy alerts. No changes are made to your URL ping test so you can continue to rely on it for alerts.
469
469
470
-
1. Once you validated the functionality of the new standard test, [update your alert rules](/azure/azure-monitor/alerts/alerts-manage-alert-rules) that reference the URL ping test to reference the standard test instead. Then you disable or delete the URL ping test.
470
+
1. Validate the functionality of the new standard test, then [update your alert rules](/azure/azure-monitor/alerts/alerts-manage-alert-rules) that reference the URL ping test to reference the standard test instead.
471
471
472
-
1. To delete a URL ping test with Azure PowerShell, you can use this command:
472
+
1. Disable or delete the URL ping test. To do so with Azure PowerShell, you can use this command:
0 commit comments