Aborted connections
—-
| Name: | Aborted connections |
| Platform: | Mysql |
| Category: | Availability |
| Description: | Checks the number of aborted client connections. |
| Long description: | Checks the number of aborted client connections. Usually this is because of incorrect password or no matching host for the user. Aborted connections can also be caused by clients trying to connect with invalid or malformed connection strings. |
| Version: | 1.2 |
| Default schedule: | 9,19,29,39,49,59 * * * |
| Requires engine install: | Yes |
| Compatibility tag: | [CDATA[.[type=‘instance’ & is_mysql_branch=‘1’]/.[hasengine=‘YES’ & use_global_variables_performance_schema = ‘1’ |
| Parameters | ||
| Name | Default value | Description |
| warning threshold | 20 | The maximum value of aborted connects (over a period of time defined by the [time threshold] parameter) before a warning is triggered. |
| alarm threshold | 100 | The maximum value of aborted connects (over a period of time defined by the [time threshold] parameter) before an alarm is triggered. |
| threshold (time) | 60 | A period of time (in minutes) which must be passed (combined with the number of aborted connects) before an alarm or a warning is returned by the procedure. |
| enable warnings and alarms | NO | If set to “NO” (default), the alert will only collect statistics without returning status warning or alarm. Value “YES” will activate the alert. |
| history threshold | 7 | The maximum number of day to kept statistics for in the historic tables. |
Job Summary
- Purpose: The purpose of this dbWatch Control Center monitoring job is to check the number of aborted client connections in the MySQL database. Aborted connections usually occur due to incorrect password usage or no matching host for the user. They can also be caused by clients attempting to connect with invalid or malformed connection strings.
- Why: This monitoring job is important to prevent unauthorized access attempts and safeguard the integrity of the database. When thresholds for aborted connections are reached, it can indicate potential security risks or configuration issues.
- Manual checking: You can check the number of aborted connections manually by running the following script: `SELECT * FROM performance_schema.global_status WHERE variable_name = ‘ABORTED_CONNECTS’`.
Job Parameters
This monitoring job enables a variety of parameters which are further described in the table below:
| Name | Default Value | SQL Type | Description |
| —- | —- | —- | —- |
| Warning threshold | 20 | 6 | Maximum number of aborted connections over a pre-defined time period before triggering a warning. |
| Alarm threshold | 100 | 6 | Maximum number of aborted connections over a pre-defined time period before triggering an alarm. |
| Threshold (time) | 60 | 5 | Time period (in minutes) which must pass (alongside exceeded aborted connections) before triggering an alarm or a warning. |
| Enable warnings and alarms | NO | 0 | Enables or disables alerts. Default is ‘NO’, which will only collect stats without issuing warnings or alarms. |
| History threshold | 7 | 5 | Maximum number of days to retain statistics data in historic tables. |
Job Dependencies
The monitoring job depends on several objects, including:
- `dbw_aborted_connects` (Main procedure)
- `dbw_aborted_connects_histr` (Dependency table)
- `dbw_aborted_connects_last` (Dependency table)
Report Generated
The job generates a report titled “Aborted connects”. The report has a default schedule and includes a presentation that details the number of aborted connections per minute. Its graph representation allows determining trend patterns and spot unusual behavior promptly. The report can be customized according to the user’s preferences.
Miscellaneous
The job falls under the category of “Availability.” It is necessary for all instances using the MySQL branch and utilizing the performance_schema. The job will force-install and replace upon installation if necessary.
Post your comment on this topic.