MySQL Process 4.x server
MySQL Process 4.x server
Log Track Supported: No
Config Track Supported: No
Custom Properties Supported: None
Supported Control Actions: None
Supported Metrics:
| Name | Alias | Units | Category | Default On | Default Interval |
|---|---|---|---|---|---|
| Availability | Availability | percentage | AVAILABILITY | true | 5 min |
| Number Of Databases | NumberOfDatabases | none | UTILIZATION | true | 30 min |
| Virtual Memory Size | VirtualMemSize | B | UTILIZATION | true | 5 min |
| Memory Size | MemSize | B | UTILIZATION | true | 5 min |
| Cpu System Time | SystemTime | ms | UTILIZATION | false | 10 min |
| Cpu System Time per Minute | SystemTime1m | ms | UTILIZATION | false | 10 min |
| Cpu User Time | UserTime | ms | UTILIZATION | false | 10 min |
| Cpu User Time per Minute | UserTime1m | ms | UTILIZATION | false | 10 min |
| Cpu Total Time | TotalTime | ms | UTILIZATION | false | 10 min |
| Cpu Total Time per Minute | TotalTime1m | ms | UTILIZATION | false | 10 min |
| Cpu Usage | Usage | percentage | UTILIZATION | true | 5 min |
| Open File Descriptors | OpenFd | none | UTILIZATION | false | 5 min |
Configuration help:
Configure MySQL 4.x for Monitoring
The MySQL 4.x plugin monitors the MySQL server using standard JDBC queries. The only prerequisites for enabling monitoring are:
- You can connect to the MySQL server as ${jdbcUser} using the JDBC URL ${jdbcUrl}
- The user ${jdbcUser} is able to issue 'SHOW STATUS' commands to MySQL
The process.query option is a PTQL statement that allows HQ to find a running MySQL server in the process table. This value is determined during autodiscovery, and should not need to be changed.
NOTE: Auto-discovery for the MySQL Process Query server will result in new servers being created for each database that is found using the SHOW DATABASES query. No services will be discovered for the MySQL Process server type.