Default Parameters for AzrCosmosDBTest

For each Azure Cosmos DB account that is configured for the target Azure subscription, this test reports the status of that account, and alerts administrators if the account's status is abnormal. Additionally, the test also tracks read/write requests to each account, measures the responsiveness of the database service to these requests, and proactively alerts administrators to potential processing bottlenecks. The database service availability is also checked periodically, and administrators instantly alerted to the unavailability of the service. Furthermore, the test also monitors the database operations performed on every account, reveals the cost of each operation, and turns administrator attention to the costliest operations in terms of resource usage. Administrator is notified if requests are throttled because the databases/containers in the account are not sized with enough provisioned throughput to process costly operations. Storage space usage of the account is also monitored, and administrators forewarned of potential space crunches. This way, the test helps administators measure and evaluate the various service level criteria for the Azure Cosmos DB service, and determine if the performance levels promised by this database service are achieved or not.

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

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

• Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored in the SUBSCRIPTION ID text box.To know the ID that maps to the target subscription, click here.

• Specify the Directory ID of the Azure AD tenant to which the target subscription belongs in the TENANT ID text box. To know how to determine the Directory ID/Tenant ID, click here.

• The eG agent communicates with the target Microsoft Azure Subscrption 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 client secret value.Specify the Application ID of the created Application in the CLIENT ID text box. To know how to determine the Application ID ,click here. Specify the client secret value in the CLIENT PASSWORD text box. To obtain the client secret value, click here.

• Confirm the CLIENT PASSWORD by retyping it in the CONFIRM PASSWORD text box.

• In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the PROXY HOST and PROXY PORT parameters. By default, these parameters are set to none , indicating that the eG agent is not configured to communicate via a proxy, by default.

• If the proxy server requires authentication, then, specify a valid proxy user name and password in the PROXY USERNAME and PROXY PASSWORD parameters, respectively. Then, confirm the password by retyping it in the CONFIRM PASSWORD text box.

• Once the necessary values have been provided, clicking on the UPDATE button will 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.