Enterprise Monitor Eases Management of MySQL Installations

 
 
By Cameron Sturdevant  |  Posted 2008-01-03 Email Print this article Print
 
 
 
 
 
 
 

Review: Enterprise Monitor enables visibility into MySQL servers as a group.

With the latest release of MySQL Enterprise Monitor, database administrators get advanced replication and database monitoring, as well as easier installation, to help manage both commercial and no-cost MySQL open-source database installations. Enterprise Monitor Fall 2007 is available with Silver, Gold and Platinum service plans. I tested the Platinum version, which has the most features and costs $4,999 per server per year.
The components of Enterprise Monitor Fall 2007, which became available last September, include a service agent, which is required for every monitored MySQL server, and a service manager that uses Java services on a single Windows or Unix server to collect MySQL and operating system data from each of the monitored MySQL servers in its domain. A MySQL database serves as a repository for the information used by the service manager to show and report on server health.
Probably one the biggest single reasons for MySQL DBAs to consider using the Enterprise Monitor is that it enables visibility into MySQL servers as a group instead of requiring administrators to log on to each system one at a time. While this kind of functionality has been standard fare in commercial databases, MySQL—which was commercialized just two years ago—takes a big step forward with this version of the Enterprise Monitor. Enterprise Monitor also offers DBAs a Web-based Enterprise Dashboard to see graphs, charts and event data about monitored servers. I used the Enterprise Dashboard to configure Enterprise Monitor to keep watch over systems and to get updates from MySQL, as well as to see events and change settings. DBAs who are running mission-critical applications on MySQL should consider using some version of the Enterprise Monitor. Its collection of expert Advisor policies, combined with features that made it easier for me to add slave systems, will likely provide significant administrative cost savings.
Click here to read more about Oracles Database 11g. Key in Enterprise Monitor are its Advisors—complex rules created to monitor and report on MySQL server administration, memory usage, performance, replication, schema and security. These rules are tuned out of the box to fit most typical MySQL server situations, but it is easy to copy and then edit rules to create custom monitors. I used the default settings in my tests. Enterprise Monitor also makes it easier to manage MySQLs hierarchical master/slave relationships, where one or more databases from a master server are automatically mirrored onto other slave servers for backup or performance reasons. Keeping track of these master/slave relationships is challenging in large environments, and improvements in this version of Enterprise Monitor provide auto-detection and grouping of master/slave relationships. I made several changes to the replication relationships among the MySQL servers in my test environment, and Enterprise Monitor was easily able to keep up with the changes in my pairings. In really large environments, in which multiple DBAs may not document every replication pairing, this type of service is invaluable. Replication Advisor rules, which are available only in the Gold and Platinum versions of Enterprise Monitor, can now indicate when binary logs are no longer needed in the replication topology. Several other incremental improvements in the Replication Advisor rules can immediately point out when database communication errors occur, helping to ensure that problems are noted and corrected. In addition to the 19 replication rules, there are more than 80 other measures that can be tracked in this version of Enterprise Monitor, including virtual memory and query cache efficiency for individual servers that can be shown as a group. The Enterprise Monitor does require an agent for every monitored MySQL server. On each of my Windows 2003 Server test systems, the agent required 7.5MB of RAM. As with most agents, the Enterprise Monitor agents require their own maintenance plan. In my tests, the service manager would work only with the agent shipped in this version of Enterprise Monitor. Earlier versions of the agent must be upgraded before they will work with the latest Enterprise Monitor components.Check out eWEEK.coms for the latest database news, reviews and analysis.
 
 
 
 
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel