MySQL / MariaDB Health

The MySQL / MariaDB Health check connects to a MySQL or MariaDB server as an ordinary client and reports whether the connection works, how long connecting takes, how many threads are connected, and how long the server has been running. The check runs on the agent device you assign it to and connects from there over TCP to the host you enter. It runs on Windows, Linux and macOS (each in x64 and Arm64), every 5 minutes by default. The database server itself does not need to be an agent device; any agent device that can reach it over the network is enough.

Prerequisites

• An account on the database server that may sign in from the agent device's address. To create the monitoring account on the database server, see Set up the database monitoring account.
• For a meaningful thread count, the account needs the global PROCESS privilege. Without it, the account sees only its own connection and the check reports one thread on every run.

Steps

1. Go to Devices and open the device.
2. Click the Checks tab → Add Check → MySQL / MariaDB Health.

Settings

The two connect-time fields sit under Connect-time thresholds in the check form.

Results

Thresholds also trigger on equality. If Warning connect time (ms) is greater than Error connect time (ms), the check swaps the two values before evaluation. Connection setup has a fixed 10-second timeout.

Metrics collected

• Connected (yes/no)
• Connect time in milliseconds
• Number of threads, counted via information_schema.PROCESSLIST
• Server uptime in seconds (status value Uptime)

Notes

• The check opens a new connection on every run and closes it afterwards.
• The host is part of the check configuration. If you assign the check to many devices through a config package, each of them connects to the same server. Assign it to a single device instead, ideally the database server itself.