Maria Event Statements Test
The Performance Schema is a feature for monitoring the database server performance and it is implemented as a storage engine on the Maria Database server. The storage engine contains a database called performance_schema, which in turn consists of a number of tables that can be queried with regular SQL statements, returning specific performance information. Whenever there is a dip in the performance of the Maria Database server, it is necessary for the administrators to check the performance schema tables for any discrepancies. Administrators can use the Maria Event Statements test to perform such a check on the performance schema tables.
This test monitors the performance schema tables of the target Maria Database server and reports the number of digest statements executing on the database server. This test also throws light on the SQL statements that are running on the performance schema tables, the statements waiting for locks and the rows affected and examined. Using this test, administrators can also figure out the FLUSH commands executed on the tables as well as the temporary tables.
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. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency. |
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 |
---|---|---|---|
Digest statements |
Indicates the number of digest statements executing on the database server. |
Number |
The Performance Schema digest is a hashed, normalized form of a statement with the specific data values removed. It allows statistics to be gathered for similar kinds of statements. |
Statements waiting for lock |
Indicates the number of statements that were waiting for a lock on the database server. |
Number |
The detailed diagnosis of this measure lists the Thread ID, Event ID, name of the event, the start time, end time, the duration of the event, the lock time of the event and the SQL statement that created the event. |
Rows affected |
Indicates the number of rows that were affected by the statements on the database server. |
Number |
|
Rows sent |
Indicates the number of rows sent by the statements on the database server. |
Number |
|
Rows examined |
Indicates the number of rows that were read during the statement execution. |
Number |
|
Statement errors |
Indicates the rate at which FLUSH commands were executed. |
Number |
|
Statements running |
Indicates the number of statements running on the database server. |
Number |
The detailed diagnosis of this measure lists the Thread ID, Event ID, name of the event, the start time, end time, the duration of the event, the lock time of the event and the SQL statement that created the event. |
Statements waited |
Indicates the number of statements that were waiting on the database server for execution. |
Number |
|
Statement warnings |
Indicates the number of statements that were executed with a warning on the database server. |
Number |
|
Temporary disk tables |
Indicates the number of implicit temporary tables that were created on the disk, while executing statements during the last measurement period. |
Number |
If the value of this measure is high, consider increasing the ‘tmp_table_size’ configuration setting for the server. |
Temporary tables |
Indicates the number of implicit temporary tables that were created in the memory created while executing statements during the last measurement period. |
Number |
|