Default Parameters for AzrWebAppTest

Azure App Service is a managed cloud service that allows you to deploy a web application and make it available to your customers on the Internet in a very short amount of time. Since such web applications are typically of a business-critical nature, customers insist on their continuous availability and peak performance at all times. To avoid customer complaints, cloud administrators should constantly check the availability, responsiveness, and resource utilization of every web application deployed on the Azure App Service, swiftly identify those applications that are experiencing availability, operational, or overall performance issues, and rapidly initiate measures to eliminate the bottleneck. The AzrWebAppTest helps administrators in this regard.

By continuously tracking the status of each web application deployed on the Azure App Service, this test points administrators to applications that are not running. Additionally, the test periodically checks the TCP connection to each web application, thereby alerting administrators to those applications that may be running, but are inaccessible over the network. HTTP responses sent by the application are also scrutinized, and HTTP errors promptly captured and reported, so that administrators can quickly figure out why an application is unavailable.

Also, by monitoring the responsiveness of applications to web requests, the test pinpoints applications that are responding slowly to these requests and why - is it because of a latent network connection? is it owing to a slow backend server? is it due to heavy request load on the application? or is poor application throughput the bottleneck? Furthermore, the test also measures the CPU usage of each web application, thus leading administrators to those applications that are hogging CPU and adversely impacting the performance of other web applications.

This page depicts the default parameters that need to be configured for the AzrWebAppTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the TENANT ID text box, specify the Directory ID of the Azure Active Directory that is associated with the subscription of the target Microsoft Azure. To know how to determine the Directory ID, refer to the Determining the Tenant ID of the target Microsoft Azure of the Monitoring Microsoft Azure document.

• The eG agent communicates with the target Microsoft Azure using JAVA API calls. To collect the required metrics, the eG agent requires an Access token in the form of an Application ID and the key value. To know more about determining the Application ID and the key refer to the Broad Steps to Determine the Access Token section of the Monitoring Microsoft Azure document. Specify the Application ID of the created Web Application in the CLIENT ID text box and the key value in the CLIENT PASSWORD text box.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.