Endpoint monitoring is a feature that enables you to monitor your website from external geo-distributed locations. This feature is uniquely different from traditional performance counter monitoring where you are monitoring metrics on the server that the website is running on. Azure Websites support up to two endpoints for endpoint monitoring. Each endpoint can
be monitored (or tested) from up to three locations. For each endpoint you want to configure a web test for, the following information is required:
- Test Name A name you will use to identify the test in the management portal.
- URL The URL you want Azure to perform tests against. This can be your root website URL, such as contoso.com, or perhaps a custom health check page.
- Test Locations The external locations you want Azure to perform the tests from. This can range from one to three locations.
- Success Criteria The HTTP status code Azure should expect to indicate a successful test. Generally, this would be HTTP 200 (OK). Optionally, you can configure a content match, which is specific text in the response that Azure can look for to determine if the test was successful.
- Alerts You can choose to enable an alert to notify by email service administrators and co-administrators on the subscription, or other administrators by specifying the email address.
IMP :: EXAM TIP
Alerts can be configured with a sensitivity setting of low (1), medium (2), or high (3). A setting of low triggers an alert when all test locations detect a failure within 15 minutes. A setting of medium triggers an alert when at least half of the test locations detect a failure in 10 minutes. A setting of high triggers an alert any time a failure is detected.
With endpoint monitoring and alerts configured, you can let Azure perform the web tests as you have configured them, and wait for an email alert if a problem is detected. However, you can also get very useful information from the management portal relating to endpoint monitoring to see how the tests are performing, if any tests have failed and why, and metrics
captured by the endpoint monitoring service.
The Web Test blade shows a graph of server response times, the number of successful tests, and the number of failed tests. The Test Locations section of the blade shows the locations the web test is being run from and the success rate in 20 minute, 1 hour, 24 hour, and 72 hour increments. The Failed Tests section will show tests that have failed per location, and you can
click each one to see the test details and learn more about why the test failed. The Web Test blade, as shown in Figure, provides a nice visual of how the web tests are performing, the number of successful tests, and the number of failed tests.
be monitored (or tested) from up to three locations. For each endpoint you want to configure a web test for, the following information is required:
- Test Name A name you will use to identify the test in the management portal.
- URL The URL you want Azure to perform tests against. This can be your root website URL, such as contoso.com, or perhaps a custom health check page.
- Test Locations The external locations you want Azure to perform the tests from. This can range from one to three locations.
- Success Criteria The HTTP status code Azure should expect to indicate a successful test. Generally, this would be HTTP 200 (OK). Optionally, you can configure a content match, which is specific text in the response that Azure can look for to determine if the test was successful.
- Alerts You can choose to enable an alert to notify by email service administrators and co-administrators on the subscription, or other administrators by specifying the email address.
IMP :: EXAM TIP
Alerts can be configured with a sensitivity setting of low (1), medium (2), or high (3). A setting of low triggers an alert when all test locations detect a failure within 15 minutes. A setting of medium triggers an alert when at least half of the test locations detect a failure in 10 minutes. A setting of high triggers an alert any time a failure is detected.
With endpoint monitoring and alerts configured, you can let Azure perform the web tests as you have configured them, and wait for an email alert if a problem is detected. However, you can also get very useful information from the management portal relating to endpoint monitoring to see how the tests are performing, if any tests have failed and why, and metrics
captured by the endpoint monitoring service.
The Web Test blade shows a graph of server response times, the number of successful tests, and the number of failed tests. The Test Locations section of the blade shows the locations the web test is being run from and the success rate in 20 minute, 1 hour, 24 hour, and 72 hour increments. The Failed Tests section will show tests that have failed per location, and you can
click each one to see the test details and learn more about why the test failed. The Web Test blade, as shown in Figure, provides a nice visual of how the web tests are performing, the number of successful tests, and the number of failed tests.
