Maria Execution Statistics Test
The test reports the sort and join operations performed on the target database server. Using this test, administrators can figure out how many table scans were performed with index and how many table scans were performed without index. Administrators can also figure out the rate at which sorting was performed by scanning the table using full table scan method.
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
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. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Sorts performed by range |
Indicates the number of sorts performed on the statements that shared a similar range. |
Number |
|
Range sort rate |
Indicates the rate at which ranges were sorted. |
Sorts/sec |
|
Sorts by full table scan |
Indicates the number of sorts performed using a full table scan. |
Number |
Full table scans may sometimes cause a huge amount of unnecessary I/O, placing a processing burden on the entire database. Therefore, a low value is desired for this measure. |
Full table scan rate |
Indicates the rate at which sorting was performed by scanning the table using full table scan method. |
Sorts/sec |
|
Sorts by merge passes |
Indicates the number of merge passes that were performed using the sort algorithm. |
Number |
|
Merge passes sort rate |
Indicates the rate at which the sort algorithm performed merge passes. |
Sorts/sec |
If this value is large you should consider increasing the sort_buffer. |
Joins not using index |
Indicates the number of joins that do not use an index. |
Number |
|
Joins performed by full table scan |
Indicates the number of joins that were performed by full table scan. |
Number |
|
Range check joins without keys |
Indicates the number of joins that were performed in a range without using the keys after each row. |
Number |
|
Table scan with index |
Indicates the number of table scans that were performed with index. |
Number |
The detailed diagnosis of this measure lists the Thread ID, Event ID, name of the event, the start time, end time and the duration of the event. |
Table scan without index |
Indicates the number of table scans that were performed without index. |
Number |
A low value is desired for this measure. |
Statements executed using good index |
Indicates the number of statements that were executed using good indexing techniques. |
Number |
|
Statements executed using bad index |
Indicates the number of statements that were executed without proper indexing techniques. |
Number |
The detailed diagnosis of this measure reveals the Thread ID, Event ID, name of the event, the start time, end time and the duration of the event. |