Aborted connections
Job details
| 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: | .[type=‘instance’ & is_mysql_branch=‘1′]/.[hasengine=‘YES’ & use_global_variables_information_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: This dbWatch Control Center job named “Aborted connections” is intended to monitor the count of aborted client connections to a database.
- Why: Client connections can be aborted due to various reasons such as wrong credentials or due to issues in the connection strings. This job can track these and send warnings or alarms if the count meets the specified thresholds.
- How: The system auto-generates alerts and collects statistics if the relevant option is enabled. If no, it will just collect statistics.
- Note: This specific job is meant to work on MySQL databases.
Long Description
The job inspects the number of aborted client connections. Such failure to connect can often ensue from incorrect password inputs or issues with matching the host for the user. Furthermore, invalid or misconfigured connection strings could also trigger the termination of client connections.
Implementation Details
This job works by maintaining two tables called `dbw_aborted_connects_histr` and `dbw_aborted_connects_last` and a procedure `dbw_aborted_connects`. The tables store the history of aborted connections and their timestamps. The procedure retrieves the current number of aborted connections, computes the difference with the previous count, stores the data, and performs checks against the specified thresholds.
If the script runs into any issues, it includes error handling provisions that will clean up any created tables and processes.
Reporting
The job includes a reporting template for “Aborted connects”. It provides a visualization of aborted connections per minute, which is useful for identifying trends and troubleshooting potential issues causing the aborts. This information is valuable for system and database administrators who need to ensure consistent connectivity for clients accessing the database.
Dependencies and Failure Clean-up
This task is dependent on the tables `dbw_aborted_connects`, `dbw_aborted_connects_histr`, and `dbw_aborted_connects_last`, and they are required for the task to function correctly. In case of failure, the job will clean up by dropping these tables.
Scheduling
The job runs every tenth minute, starting from the 9th minute of each hour.