The Wait Ms Per Sec alert notifies you when its configured condition is met on MySQL and MariaDB instances so you can investigate and respond.
Mini DBA describes this alert as: Wait Milliseconds Per Sec (multiple cores will make it potentially greater than 1000 Ms) The MaxThreshold represents the number of Milliseconds requests wait per second that will trigger the alarm Mini DBA evaluates this alert once a minute so changes are detected quickly.
This alert reports aggregate database wait time per second. It signals that work is spending more time waiting, but the top wait categories must be inspected before assuming the cause is locking.
Enable it on any monitored MySQL and MariaDB instance where this condition would require an administrator to investigate or communicate with the application team. Tune noisy development systems after you have a short baseline.
Threshold meaning: Ms per second. Major threshold: 8000 milliseconds. Comparison direction: over. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.
Open the wait and activity views, identify the wait categories and workloads responsible, then follow the response for that subsystem. Address locking, storage, CPU scheduling, network, or concurrency only when the observed waits support that diagnosis.
If this alert is noisy, check whether the workload naturally has short bursts. Raise the duration or threshold for expected batch windows, but keep a lower route for production systems where user-facing latency matters. Avoid simply disabling the alert until you know whether the noise is caused by threshold choice or by a real capacity trend.