Azure SQL Resource Statistics Test
This test monitors how effectively the Microsoft Azure SQL database utilizes the session and process resources it is configured with. If the maximum limit to which the resource allocation can grow is violated, it is bound to deteriorate the performance of the database service, as the service might not have the bandwidth to handle the additional sessions/processes.
Target of the test : A Microsoft Azure SQL database
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the Azure SQL database configured for monitoring
| Parameters | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port at which the specified Host listens. |
|
Database Name |
Specify the name of the Azure SQL database that is to be monitored. |
|
User Name and Password |
Against the User Name and Password parameters, specify the credentials of the user who is vested with DBOWNER rights to the configured Database Name. |
|
Confirm Password |
Confirm the specified Password by retyping it here. |
|
SSL |
If the Azure SQL database service being monitored is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No. |
|
Domain |
By default, none is displayed in this text box. If the ‘SQL server and Windows’ authentication has been enabled for the Azure SQL database being monitored, then the Domain parameter can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the Domain text box, specify the Windows domain in which the monitored database exists. Also, in such a case, the User Name and Password that you provide should be that of a 'domain user' with DBOWNER rights to the configured Database Name. |
|
IS NTLMv2 |
In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 (“NTLMv2”) was concocted to address the security issues present in NTLM. By default, this flag is set to No, indicating that NTLMv2 is not enabled by default for the target Microsoft Azure SQL database. Set this flag to Yes if NTLMv2 is enabled for the target database. |
|
Azure AD Authentication |
This parameter indicates whether Azure Active Directory (Azure AD) authentication should be used to connect to the Azure SQL Database. If this parameter is set to Yes, the agent will authenticate to the Azure SQL Database using an Azure AD user / domain-based credentials. In this case, the Truststore File Name and Truststore Password parameters must also be configured. If this parameter is set to No, standard SQL authentication will be used. By default, this parameter is set to No. |
|
Truststore File Name |
This parameter is applicable only when Azure AD authentication is set to Yes. If not, set this parameter to none. When Azure AD authentication is used, the server certificate presented by the Azure SQL database during TLS connection establishment must be trusted. For this purpose, the agent must have access to the truststore that contains the CA certificates required to authenticate the Azure SQL server. In this text box, specify the name of the truststore file that contains these trusted CA certificate entries. For example: combinedTrustStore.jks. By default, none is displayed against this text box. To know more, refer to How Does eG Enterprise Monitor a Microsoft Azure SQL Database?. |
|
Truststore Password |
This parameter is applicable only when Azure AD authentication is set to Yes. If not, set this parameter to none. If a truststore file is provided in the Truststore File Name text box, then specify the password that is required to access the certificate entries stored in that truststore file. This password is used by the agent to open the truststore and retrieve the certificates for validating the Azure SQL server during authentication. By default, this parameter is set to none. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Average CPU usage |
Indicates the average compute utilization in percentage of the limit of the service tier of the database. |
Percent |
A value close to 100% implies that the Azure SQL database is consuming CPU excessively. |
|
Average data IO usage |
Indicates the average I/O utilization in percentage based on the limit of the service tier of the database. |
Percent |
A value close to 100% implies that the Azure SQL database is hogging I/O resources. |
|
Average memory usage |
Indicates the average memory utilization in percentage of the limit of the service tier of the database instance. |
Percent |
A value close to 100% implies that the Azure SQL database is over-utilizing memory resources. |
|
Average of log write |
Indicates the average resource utilized in percentage for writes of the limit of the service tier of the database. |
Percent |
|
|
Current DTU limit |
Indicates the current maximum database DTU setting in percentage for the database during this interval. |
Percent |
|
|
DTU usage |
Indicates the percentage of DTU utilized by the database. |
Percent |
|
|
Workers usage |
Indicates the maximum concurrent workers (requests) in percentage of the limit of the service tier of the database. |
Percent |
|
|
Sessions usage |
Indicates the maximum concurrent sessions in percentage of the limit of the service tier of the database. |
Percent |
|