DBA team wants to know that how the myisam_total_disk_write_ratio checkpoint value is calculated.
What query is being used to fetch the information by the probe?
Actually this checkpoint is repeatedly generating alarm. The current value is hovering around 3.5% only and threshold is set at <=70
The alarm for a value of 3.5% is correct.
Please see MySQL documentation below:
check myisam_total_disk_write_ratio checkpoint
Below is the description.
Ratio of disk writes to all write requests.
Calculated as: Key_writes/Key_write_requests
Also review the following link for reference:
>>The ratio of the number of physical writes of a key block to the cache to the number of requests to write a key block to the cache in percentage. For a good performance of the MySQL server, the value of Key Write Efficiency must be 90 percent and above.<<
So the <= threshold operator is correct
Monitors the ratio of disk writes to all write requests .
Attached is a kb article with all of the queries used by the mysql probe for review.
KB136531 : mySQL probe Checkpoint Queries
From the attached document, it specifies the following:
The probe is using the MYSQL query SHOW GLOBAL STATUS to get the information for this QOS.
So to find the information, execute a query such as:
available" -> Just to check whether connection is possible or not.
The probe then uses code to count the databases.
The probe issues SHOW GLOBAL STATUS
then goes through the data returned to find the value it is looking for such as
There is no more information to provide.
This is why the mysql probe Release Notes documents the following:
The mysql user configured in probe must have access to the following queries on the mysql server.
SHOW GLOBAL STATUS
SHOW SLAVE STATUS
SELECT TABLE_NAME, AVG_ROW_LENGTH, DATA_LENGTH, MAX_DATA_LENGTH, INDEX_LENGTH, DATA_FREE, TABLE_SCHEMA FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE' AND MAX_DATA_LENGTH > 0 ORDER BY TABLE_SCHEMA ASC
This is what the probe is using to pull the information for the monitored mySQL database.