Maria Queries Test

This test reports the performance statistics pertaining to the queries executed on the Maria Database 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 database being monitored.

Configurable parameters for the test
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 section.

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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Query rate

Indicates the rate at which queries are sent to the server.

Queries/Sec

This is an indicator of server workload.

Slow queries

Indicates the number of queries that have taken more than the ‘long_query_time’ for execution, during the last measurement period.

Number

This value should ideally be 0. If it remains consistently high, the administrator should look to identify and optimize the slow queries.

Index first entry read count

Indicates the number of times the first entry was read from an index during the last measurement period.

Number

If the value of this measure is high, it suggests that the server is doing a lot of full index scans.

Row read requests based on a key

Indicates the number of requests that were received in the last measurement period, to read a row based on a key.

Number

If the value of this measure is high, it indicates that your queries and tables are properly indexed.

Next row read requests based on key order

Indicates the number of requests received in the last measurement period, to read the next row in the key order.

Number

This will be incremented if you are querying an index column with a range constraint. This will also be incremented if you are doing an index scan.

Previous row read requests based on key order

Indicates the number of requests received in the last measurement period, to read the previous row in the key order.

Number

This is mainly used to optimize ORDER BY... DESC.

Row read requests based on a fixed position

Indicates the number of requests received in the last measurement period, to read a row based on a fixed position.

Number

This will be high if you are executing a lot of queries that require sorting of the result. If the value of this measure is high,  then you probably have a lot of  queries that require Maria database server to scan whole tables or you have joins that do not use keys properly.

Next row read requests in the datafile

Indicates the number of requests received in the last measurement period, to read the next row in the datafile.

Number

This will be high if you are performing a lot of table scans. Generally, this suggests that your tables are not properly indexed or that your queries are not written to use the indexes properly.