Maria Connections Test
Monitoring client connections to a Maria Database server typically provide insights into the workload of the server and whether/not the server is sized well-enough to handle the load. This is exactly the type of visibility the Maria Connections test provides. This test tracks client connections to the target server and reports their usage. With the help of the metrics reported by this test, administrators can assess the load on the server and can determine whether/not the server has sufficient free connections to handle subsequent connection requests. Based on these insights, administrators can plan the future connection capacity of the server.
Target of the test : A Maria Database server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the Maria Database server being monitored
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the Maria Database server. |
Port |
The port on which the server is listening |
Database |
Specify the name of the database that is to be monitored on the target Maria Database server |
User and Password |
The eG agent has to be configured with the credentials of a user who has server-wide PROCESS and SELECT privileges on the monitored Maria Database server. To know how to create such a user, refer to Configuring the eG Agent with Access Privileges |
Confirm Password |
Confirm the password by retyping it here. |
SSL |
This indicates that the eG agent will communicate with the Maria Database via HTTPS or not. By default, this flag is set to No, as the target Maria database is not SSL-enabled by default. If the target database is SSL-enabled, then set this flag to Yes. |
Verify CA |
If the eG agent is required to establish an encrypted connection with the target Maria Database server by authenticating the server's identity through verifying the server CA certificate, set Verify CA flag to Yes. By default, this flag is set to No. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Active connections |
Indicates the count of incoming connections that were opened by the clients to the server. |
Number |
This is a good measure of the current load on the server. A persistent high value or a bottleneck in the server is an indication for the administrator to check if the connections are not closed properly. |
Connections aborted |
Indicates the number of connections that were aborted due to the client terminating the connection instead of closing the connection during the last measurement period. |
Number |
|
Connections create rate |
Indicates the rate at which connections were created to connect to the server from the clients during the last measurement period. |
Connections/sec |
|
Connections failed |
Indicates the number of connection that failed on the server during the last measurement period. |
Number |
A high value of this measure may be an indication of either a configuration problem with the server/clients or some malicious attack on the server. |
Maximum connections |
Indicates the maximum number of connections that were simultaneously in use on the server during the last measurement period. |
Number |
|