Andy Bang, Sloan Childers, Darren Oldag, Eric Herman, Jan Kneschke, Kay Roepke, Mark Matthews, Bill Weber, Diego Medina, Marcos Palacios, Carsten "Pino" Segieth, Josh Sled, Keith Russell, Mark Leith, Heidi Bergh-Hoff, and Gary Whizin (and also welcome Michael Schuster!)
Yet another great job guys!
The new version, 2.1, was posted as GA early on Tuesday and it is quite possibly the best release of the Enterprise Monitor to date.
For those not familiar with the Enterprise Monitor, it is included in a MySQL Enterprise subscription and is a distributed web-based app that users deploy in their environment to monitor and tune the security, performance and availability of their dev, QA and production MySQL servers. It is comprised of :
- An agent, written in C, that is installed on each monitored data source, which collects MySQL and OS metrics, SQL code and exec results
- A central server (aka "service manager"), written in Java, that collects, monitors and alerts on the data collected by each agent. The service manager uses MySQL Best Practice Advisors to measure the collected data against user-defined thresholds and to proactively notify DBAs of problems or tuning opportunities. Alerts are sent to a central console or via SMTP or SNMP notifications.
- A repository that holds the data collected by each agent. The service manager monitors the data stored in repository vs maintaining a persistent connection to each MySQL server.
Based on customer interviews and years spent in the field, we understand the pain associated with finding bottlenecks rooted in poorly written or inefficient SQL code (this is consistently the #1 problem we hear when talking with MySQL DBAs and devs.) This new release helps a DBA/Dev spend less time "finding" and more time "fixing" poorly performing queries. The key new features in the Query Analyzer include:
- Clickable MySQL and OS graphs that visual correlation system and query activity. Mouse-over a spike in any graph and drill into the queries that were running at the same time. Big time saver.
- Drill down capability for query specific executions – drill into any query and see execution specific graphs for exec time, count, data returned. Helps you see the "normal" exec pattern for a query and identify outliers that may occur during specific windows or time or for specific variable combinations.
- Counts for SQL errors/warnings - help you quickly identify queries that may have never finished or that finished in error. These routinely go undetected by the MySQL logs, etc.
- UI support for EXPLAIN generation threshold - gone are the days of hacking the quan.lua script to set this value!
The new release also includes an updated "What's New" page that allows you to optionally subscribe to live feeds for your open support issues (nice, especially for the issues with a status of "waiting on customer") and for MySQL product updates and alerts. Nice time saver, especially for getting updates on new releases of the Enterprise Server and for Monitor Advisors and graphs.
So how do you get it? Glad you asked...if you are an Enterprise subscriber you can grab the new release and all of the updated docs from the Enterprise Customer download page. If you are interested in learning more or want to try the new Monitor and Query Analyzer for yourself, you can register for a 30 day trial subscription which includes a fully functioning version of the Monitor and Query Analyzer. You also learn everything about MySQL Enterprise by visiting the MySQL web site.
Look forward to hearing about your experience with the new release!
4 comments:
Rob,
Be less humble. If this isn't the best release it shouldn't have been released.
What options are available to import queries (only via the proxy, via other sources)? I don't like to put extra processes between my production apps and db servers. I have other ways to get the queries though.
Mark,
There's a way to do this, starting with version 2.0 via a REST API. MC brown has blogged about an example using DTrace and Perl, but the mechanism is the same no matter what your source, see http://coalface.mcslp.com/2008/11/15/feeding-query-analyzer-from-dtrace/
"There is a Replication Monitor that proactively monitors replication topologies for synch and performance issues"
What does it mean that it monitors for replication synch and performance issues?
Hi Baron,
The replication monitor auto-discovers and groups your master/slave topologies in hierarchy order and gives you stats for slave seconds behind master, binlog pos, up/down status, status of SQL/IO thread, last error, etc. The repl monitor also syncs up with the Monitor replication advisors so you can get status details if/when you get an advisor related event or notification. The single point of view keeps you out of the CLI to pull the needed info together.
You can see it here.
(apologies in advance if you are asked to register to view the demo)
Post a Comment