The MySQL Restarted 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: MySQL has restarted recently. Unexpected restarts can indicate crashes, failovers, patching, memory pressure, or manual maintenance that applications may have felt as an outage. Mini DBA evaluates this alert once a minute so changes are detected quickly.
This alert protects availability by warning when Mini DBA cannot reach the monitored MySQL and MariaDB instance or when the service state changes unexpectedly. It is often the first signal that users will see connection failures before deeper diagnostic metrics can be collected.
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: Seconds since restart. Major threshold: 300 seconds. Comparison direction: under. For an under-threshold alert, increasing a threshold makes that severity fire sooner; decreasing it waits until the value falls further. Set the minor threshold as an early-warning level and the major threshold at the lowest acceptable value for the service.
Open the related Mini DBA page for the instance, compare the current value with the recent baseline, identify whether the change is caused by workload, configuration, host capacity, or maintenance, then record the corrective action in the incident notes.
If the alert creates repeated noise, review whether it is enabled on the correct instances, whether maintenance windows are configured, and whether the minor and major routes match the real business impact. Keep enough history to prove the new setting before changing it broadly.