Standard tests are a single request test that is similar to the URL ping test but more advanced. In addition to validating whether an endpoint is responding and measuring the performance, Standard tests also includes SSL certificate validity, proactive lifetime check, HTTP request verb (for example
POST, etc.), custom headers, and custom data associated with your HTTP request.
To create an availability test, you need use an existing Application Insights resource or create an Application Insights resource.
If you are currently using other availability tests, like URL ping tests, you may add Standard tests along side the others. If you would like to use Standard tests instead of one of your other tests, add a Standard test and delete your old test.
Create a Standard test
To create a standard test:
Go to your Application Insights resource and select the Availability pane.
Select Add Standard test.
Input your test name, URL and other settings (explanation below), then select Create.
|URL||The URL can be any web page you want to test, but it must be visible from the public internet. The URL can include a query string. So, for example, you can exercise your database a little. If the URL resolves to a redirect, we follow it up to 10 redirects.|
|Parse dependent requests||Test requests images, scripts, style files, and other files that are part of the web page under test. The recorded response time includes the time taken to get these files. The test fails if any of these resources can't be successfully downloaded within the timeout for the whole test. If the option isn't checked, the test only requests the file at the URL you specified. Enabling this option results in a stricter check. The test could fail for cases, which may not be noticeable when manually browsing the site.|
|Enable retries||When the test fails, it's retried after a short interval. A failure is reported only if three successive attempts fail. Subsequent tests are then performed at the usual test frequency. Retry is temporarily suspended until the next success. This rule is applied independently at each test location. We recommend this option. On average, about 80% of failures disappear on retry.|
|SSL certificate validation test||You can verify the SSL certificate on your website to make sure it's correctly installed, valid, trusted, and doesn't give any errors to any of your users.|
|Proactive lifetime check||This setting enables you to define a set time period before your SSL certificate expires. Once it expires, your test will fail.|
|Test frequency||Sets how often the test is run from each test location. With a default frequency of five minutes and five test locations, your site is tested on average every minute.|
|Test locations||The places from where our servers send web requests to your URL. Our minimum number of recommended test locations is five to ensure that you can distinguish problems in your website from network issues. You can select up to 16 locations.|
|Custom headers||Key value pairs that define the operating parameters.|
|HTTP request verb||Indicate what action you would like to take with your request.|
|Request body||Custom data associated with your HTTP request. You can upload your own files, type in your content, or disable this feature.|
|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, then all the images, style files, scripts, and other dependent resources must have been received within this period.|
|HTTP response||The returned status code that is counted as a success. 200 is the code that indicates that a normal web page has been returned.|
|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|
|Near-realtime||We recommend using Near-realtime alerts. Configuring this type of alert is done after your availability test is created.|
|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.|
Location population tags
The following population tags can be used for the geo-location attribute when deploying an availability URL ping test using Azure Resource Manager.
|Display Name||Population Name|
|Display Name||Population Name|
|China East 2||mc-cne2-azr|
|China North 2||mc-cnn2-azr|
|Display Name||Population Name|
|France South (Formerly France Central)||emea-ch-zrh-edge|
|North Central US||us-il-ch1-azr|
|South Central US||us-tx-sn1-azr|
See your availability test results
Availability test results can be visualized with both line and scatter plot views.
After a few minutes, select Refresh to see your test results.
The scatterplot view shows samples of the test results that have diagnostic test-step detail in them. The test engine stores diagnostic detail for tests that have failures. For successful tests, diagnostic details are stored for a subset of the executions. Hover over any of the green/red dots to see the test, test name, and location.
Select a particular test, location, or reduce the time period to see more results around the time period of interest. Use Search Explorer to see results from all executions, or use Analytics queries to run custom reports on this data.
Inspect and edit tests
To edit, temporarily disable, or delete a test, select the ellipses next to a test name. It may take up to 20 minutes for configuration changes to propagate to all test agents after a change is made.
You might want to disable availability tests or the alert rules associated with them while you're performing maintenance on your service.
If you see failures
Select a red dot.
From an availability test result, you can see the transaction details across all components. Here you can:
- Review the troubleshooting report to determine what may have caused your test to fail but your application is still available.
- Inspect the response received from your server.
- Diagnose failure with correlated server-side telemetry collected while processing the failed availability test.
- Log an issue or work item in Git or Azure Boards to track the problem. The bug will contain a link to this event.
- Open the web test result in Visual Studio.
To learn more about the end to end transaction diagnostics experience, visit the transaction diagnostics documentation.
Select on the exception row to see the details of the server-side exception that caused the synthetic availability test to fail. You can also get the debug snapshot for richer code level diagnostics.
In addition to the raw results, you can also view two key Availability metrics in Metrics Explorer:
- Availability: Percentage of the tests that were successful, across all test executions.
- Test Duration: Average test duration across all test executions.
Submit and view feedback for