#### Table of contents
1. [Overview] (#overview)
2. [Usage] (#usage)
3. [Notices] (#notices)
4. [Installation] (#installation)
5. [Development] (#development)
## Overview
This program scan and report all the TINYINT, SMALLINT, MEDIUMINT, INT, BIGINT columns where the highest value is too
close from the highest possible value allowed by the column type.
It handles UNSIGNED and SIGNED cases.
## Usage
```
usage: monitor.py [-h] [--username USERNAME] [--password [PASSWORD]]
[--host HOST] [--threshold THRESHOLD]
[--exclude EXCLUDE [EXCLUDE ...]] [--db DB [DB ...]]
optional arguments:
-h, --help show this help message and exit
--username USERNAME, -u USERNAME
MySQL username
--password [PASSWORD], -p [PASSWORD]
MySQL password
--host HOST MySQL host
--threshold THRESHOLD, -t THRESHOLD
The alerting threshold (ex: 0.8 means alert when a
column max value is 80% of the max possible value
--exclude EXCLUDE [EXCLUDE ...], -e EXCLUDE [EXCLUDE ...]
Database to exclude separated by a comma
--db DB [DB ...], -d DB [DB ...]
Databases to analyse separated by a comma (default
all)
```
## Notices
BE CAREFUL:
- It could be very slow (especially on heavy loaded servers or servers with a huge databases/tables count.
You surely want to run this tool on a slave instead of a master
- This script disable innodb_stats computing for optimizing performance_schema analysis and enable it at the end
See: http://www.percona.com/blog/2011/12/23/solving-information_schema-slowness/
If you interrupt this script (Ctrl+C ...) it is up to you to reactivate it using something like:
set global innodb_stats_on_metadata=1;
## Installation
To install it with a [Python virtualenv](http://docs.python-guide.org/en/latest/dev/virtualenvs/) (recommended):
```
$> virtualenv myenv
$> source myenv/bin/activate
(myenv) $> pip install mysql-monitor
(myenv) $> mysql-monitor -h
```
Or on your system, without virtualenv:
```
$> pip install mysql-monitor
$> mysql-monitor -h
```
## Development
To start hacking on the project, run:
```
$> virtualenv myenv
$> source myenv/bin/activate
(myenv) $> pip install -e .
(myenv) $> mysql-monitor -h
```
Changelog
=========
0.1.0 (unreleased)
------------------
Initial version.
Metadata
Release files for monitor-mysql-overflows 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| monitor-mysql-overflows-1.1.1.tar.gz | 5.3 kB | Without provenance | Details |
Release files / monitor-mysql-overflows-1.1.1.tar.gz
| Download URL | monitor-mysql-overflows-1.1.1.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b493b650001ac3efe3361f4c6bc50fdb98fccb07e88f6a4ca5071d16316d699
|
|
BLAKE2b-256 checksum How to use checksums |
097a0438dec3658278eeba633f24eaf645602647f7004bdba9d18d851dff0f88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for monitor-mysql-overflows 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.