Maria Cache Test

This test monitors the key buffer cache in the Maria Database server and reports the number of physical reads of a key block, the number of read requests received by the cache and the number of key blocks that have been modified but not flushed to the cache. Using this test, administrators can figure out data mismatch between the cache and the disk and rectify the same before end users start complaining about outdated data from the disk.

Target of the test : A Maria Database server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Maria Database server 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
Key read requests	Indicates the number of physical reads of a key block from the disk instead of the cache during the last measurement period.	Number	A high value for this measure indicates that the key_buffer_size variable is probably too small to cache the data.
Key reads	Indicates the number of reads requests received by the cache during the last measurement period.	Number	The higher the count, the better the performance of the server, as it does not need to read the requested key data from disk.
Not flushed key blocks	Indicates the number of key blocks that have been modified in the cache but have not been flushed to the disk during the last measurement period.	Number	A high value for this measure indicates a mismatch of data between the cache and the disk. If the value of this measure increases in a steep manner, then, there may be a mismatch in the data received by the users since the disk may not be updated as son as the data in the cache is modified.