This section describes the expression-based Availability Advisors.
Aborted connection attempts to MySQL may indicate an issue with respect to the server or network, or could be indicative of DoS or password-cracking attempts against the MySQL Server. The aborted-connects count is incremented when:
A client does not have privileges to access a database
A client uses the wrong password
A malformed packet is received
The
connect_timeout
variable is exceeded
Default frequency 00:05:00
Default auto-close enabled no
Excess aborted connection attempts to MySQL may indicate an issue with respect to the server or network, or could be indicative of DoS or password-cracking attempts against the MySQL Server. The aborted-connects count is incremented when:
A client does not have privileges to access a database
A client uses the wrong password
A malformed packet is received
The
connect_timeout
variable is exceeded
Default frequency 00:05:00
Default auto-close enabled no
Once the maximum connection limit for the MySQL server has been reached, no other user connections can be established and errors occur on the client side of the application.
Default frequency 00:05:00
Default auto-close enabled yes
Tracks MySQL availability, by making a full connection to the monitored instance on the configured frequency.
The Availability statistics on the main Dashboard Overview page require this advisor to be enabled.
Default auto-close enabled yes
To perform useful work, a database server must be up-and-running continuously. It is normal for a production server to run continuously for weeks, months, or longer. If a server has been restarted recently, it may be the result of planned maintenance, but it may also be due to an unplanned event that should be investigated.
Default frequency 00:05:00
Default auto-close enabled no