Use the MySQL Restarted alert in Mini DBA to monitor MySQL and MariaDB instances and make this condition visible before it becomes a wider database incident.
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. The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage.
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". Use higher thresholds on batch-heavy, development, or intentionally bursty systems where brief pressure is expected. Use lower thresholds on latency-sensitive production systems, small instances with little headroom, and services with strict recovery or availability commitments.
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.