Aborted connections
Job details
| Name: | Aborted connections |
| Platform: | Mariadb |
| 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_mariadb_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: The purpose of this job is to monitor aborted client connections to a MariaDB database, identifying failures due primarily to incorrect authentications or unauthorized connection attempts.
- Why: This job is critical for maintaining the security and accessibility of the database. Excessive aborted connections can indicate potential unauthorized access attempts or misconfigurations, which could lead to service disruption or security breaches.
- Manual checking: You can manually check the current number of aborted connections through the MariaDB’s information schema by executing:
SELECT VARIABLE_VALUE FROM information_schema.global_status WHERE variable_name = 'ABORTED_CONNECTS';Detailed Description
This monitoring job checks the count of aborted connections that could not be established with the server. Common causes for aborted connections:
- Incorrect password entries
- No matching host found for the username
- Invalid or malformed connection strings from the clients
Implementation Details
- The job deploys several SQL scripts and procedures to efficiently track and store data regarding aborted connections.
- It creates historical tracking tables and last checked values for comparative analysis over set intervals. This analysis helps in recognizing patterns or spikes in aborted attempts.
Clean-up On Failure
- Should there be a failure in setting up the job, the following clean-up operations are performed:
- “DROP TABLE“ commands to remove any partially created tables.
Thresholds and Alarms
- A “warning” is generated if the number of aborted connections exceeds a predefined threshold over a specified time window.
- An “alarm” is raised if the number of aborted connections passes a higher threshold, indicating more immediate attention is required.
- Warning and alarm alerts can be toggled on or off, providing flexibility in monitoring intensity and notifications.
Monitoring and Reporting
- Continual monitoring is configured by default to check status in defined minute intervals.
- A special report visually presents the data, showing the number of aborted connections per minute over time, allowing for quick identification of issues or anomalies.
Dependencies and Pre-requisites
- This job requires specific database objects (procedures and tables) in place for tracking and logging aborted connections.
- It automatically checks compatibility with the current database instance to ensure all prerequisites for monitoring are met before installation.
Maintenance
- Outdated records are purged from the database to maintain optimal performance and accuracy in reporting, adhering to a specified history threshold.
Security and Integrity
- The implementation details and specific scripts are managed sensitively, ensuring that monitoring does not interfere with database performance or security.
This control center job is essential for administrators to maintain the health, performance, and security of their MariaDB databases, ensuring robust and reliable database connectivity.