Added some new code to Kontrollbase to allow you to view the cnf file on each host, as well as all of the global variables and global status information that was collected from the most recent polling period. Here are some screencaps.
A nice write up here: http://www.masterzen.fr/2009/04/13/introducing-mysql-snmp/ “It’s a Net-SNMP perl subagent that connects to your MySQL server, and reports various statistics (from show status or show innodb status, or even replication) through SNMP.”
This might find its way into Kontrollbase soon…
Monolith: MySQL server monitoring. I only have servers that run Redhat/Debian/Ubuntu Linux x86 and x86_64. I don’t have machines to test MySQL monitoring for the following OSes. Perhaps you would like to be a test candidate for the new version of Monolith? If so, let me know and you’ll be on the list, as well as get beta testing credit.
OSX Server: PPC and Intel
AIX
FreeBSD / OpenBSD / NetBSD
Windows Server
Solaris: Intel & Sparc
Linux servers that are NOT Intel based.
What this involves: testing the client script, perl modules, snmp stats, and other functions that may require a custom client script for that architecture.
What would you like to see in a free enterprise-grade monitoring system for your daily MySQL needs?I’m rewriting Monolith – MySQL DBA Console from the ground up. This will be version 2 and I would like to get some input from the global MySQL community.So far I am going with the following; comment with any improvements/additions.
- Variable interval polling of server statistics
- Over 50 different alerts (see list below)
- Graphing of various server statistics (see list below)
- Tuning recommendations with cnf file changes to apply to server
- Change control documents for recommended performance/security tuning
- Threshold based alerting with multiple alert groups: info,warn,critical
- Sorting/ordering of servers via groups. ie: client -> dev,stage,prod
- RSS feeds for each alert group
- XML export with user defined fields for external applications (API of sorts)
- Slave server alerts, IO thread / SQL thread, seconds behind master (with threshold)
- Various general stats: version, system ram size, # of schema, default table type
- Ability to view current cnf file from server
- Ability to view current global variables as a list
- Email / pager reporting for alerts (choose warn/crit alerts to report on)
Alerts - can be enabled or disabled for reporting on a per server basis
- number of connection failures (threshold)
- number of connections errors (threshold)
- binary logging not enabled
- sync_binlog not set
- max_used_connections too high compared to max_connections (ratio over 85% utilization)
- query cache size too small: improper utilization
- query cache size too large: improper utilization
- memory usage over 85% of system ram
- table scans excessive
- tmp table to disk ratio too high
- innodb buffer too small
- innodb buffer too large (resources can be used elsewhere)
- key buffer too large (resources can be used elsewhere)
- key buffer too small
- sort buffer too small
- sort buffer too large (resources can be used elsewhere)
- join buffer too small
- join buffer too large (resources can be used elsewhere)
- open_files_limit too small compared to open_files usage ratio
- table locks too high
- table cache too small
- table cache too large (resources can be used elsewhere)
- thread cache too small
- thread cache too large (resources can be used elsewhere)
- binlog size too small
- excessive disk tmp table usage
- flush time not zero value
- indexes not being utilized properly
- innodb doublewrite buffer enabled
- innodb flush method not properly set
- innodb transaction isolation level not properly set for ACID
- innodb log wait time too high
- conncurrent insert not set correctly
- query cache not enabled
- table locks too high
- thread cache not enabled
- concurrent queries too high (threshold)
- binary logs not set to auto-purge
- binary logging not enabled
- slave not active if server is set to slave
- slave sql thread stopped
- slave io thread stopped
- slave behind master too long (threshold)
- slave not set as read-only
- slave relay logs not automatically purged
- account has global privs
- account set to old_password
- accounts able to be added with empty password
- account has grant option
- root can login remotely
- root has no password
- blank username detected
- test database exists
- usage user exists
- general query log enabled
- CPU usage over threshold
- Load Average over threshold
Graphs - default
- Query cache utilization, in/out hit ratio
- Temp tables usage
- Temp files usage
- Open tables usage
- Thread cached / created
- Connections
- Query rate
- Data size, Index size, overall size
- Uptime
- CPU usage
- I/O usage
- Load average
- Data transfer in/out
- Memory allocation
- Swap usage
- Slave delay (if configured as a slave)
As mentioned before, this is a OSS application that has no license or subscription fees and will be updated on a regular basis. It’s a mix of PHP for the web side and Perl for the system polling and reporting processes. The installer will be new, web based, and a simple process, much improved from the current method.Please add your comments now, as I am drawing up plans this week for version 2. 
Current Books in Review
