List:Announcements« Previous MessageNext Message »
From:andy bang Date:December 5 2013 11:11pm
Subject:MySQL Enterprise Monitor 3.0.4 Is Now Available
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.0.4 is now
available for download on the My Oracle Support (MOS) web site.  It
will also be available via the Oracle Software Delivery Cloud with the
December update in about 1 week.

This is a maintenance release that adds a few features and fixes a
number of bugs.  You can find more information on the contents of this
release in the change log:

     http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-news-3-0-4.html
     (also included at the end of this note for convenience)

You will find binaries for the new release on My Oracle Support:

     https://support.oracle.com

Choose the "Patches & Updates" tab, and then use the "Product or
Family (Advanced Search)" feature.

You will also find the binaries on the Oracle Software Delivery Cloud
in approximately 1 week:

     http://edelivery.oracle.com/

Choose "MySQL Database" as the Product Pack and you will find the
Enterprise Monitor along with other MySQL products.

Based on feedback from our customers, MySQL Enterprise Monitor (MEM)
3.0 offers many significant improvements over previous releases.
Highlights include:

o Policy-based automatic scheduling of rules and event handling
   (including email notifications) make administration of scale-out
   easier and automatic

o Enhancements such as automatic discovery of MySQL instances,
   centralized agent configuration and multi-instance monitoring
   further improve ease of configuration and management

o The new cloud and virtualization-friendly, "agent-less" design
   allows remote monitoring of MySQL databases without the need for any
   remote agents

o Trends, projections and forecasting - Graphs and Event handlers
   inform you in advance of impending file system capacity problems

o Zero Configuration Query Analyzer - Works "out of the box" with
   MySQL 5.6 Performance_Schema (supported by 5.6.14 or later)

o False positives from flapping or spikes are avoided using
   exponential moving averages and other statistical techniques

o Advisors can analyze data across an entire group; for example, the
   Replication Advisor can scan an entire topology to find common
   configuration errors like duplicate server UUIDs or a slave whose
   version is less than its master's

More information on the contents of this release is available here:

   What's new in MySQL Enterprise Monitor 3.0?
   http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-comparison-2-3.html

   MySQL Enterprise Edition: Demos
   http://www.mysql.com/products/enterprise/demo.html

   MySQL Enterprise Monitor Frequently Asked Questions
   http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-faq.html

   MySQL Enterprise Monitor Change History
   http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-news.html

More information on MySQL Enterprise and the Enterprise Monitor can be
found here:

   http://www.mysql.com/products/enterprise/
   http://www.mysql.com/products/enterprise/monitor.html
   http://www.mysql.com/products/enterprise/query.html
   http://forums.mysql.com/list.php?142

If you are not a MySQL Enterprise customer and want to try the Monitor
and Query Analyzer using our 30-day free customer trial, go to
http://www.mysql.com/trials, or contact Sales at
http://www.mysql.com/about/contact.

If you haven't looked at 3.0 recently, please do so now and let us
know what you think.

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.0.4

Functionality Added or Changed

* A new Unreachable Agents section was added to the MySQL Instances
   dashboard. It is only visible if there are unreachable Agents. This
   section displays information about the unreachable Agents, and
   provides a Delete Agent action. (Bug #17662013)

* The mysql-identity-source Agent Installer (unattended) and agent.sh
   option was added. It determines how the unique identity for the
   MySQL instance is determined. The default option uses either the
   "server_uuid" variable if present, or generates a random new one.
   Passing in host_and_datadir uses a hash of the host identity and the
   path to the MySQL instance's data (datadir) directory.

   For example, passing in host_and_datadir allows a MySQL instance to
   preserve its history in MySQL Enterprise Monitor if it is rebuilt,
   as the host and datadir are the same, thus the hash will be
   identical.

   Note: host_and_datadir is not allowed when the Agent is remote
   monitoring a MySQL instance, as MySQL Enterprise Monitor is unable
   to definitively compute a known-unique host identity in this case.
   (Bug #17558993, Bug #70507)

Bugs Fixed

* Made --socket usage improvements with agent.sh, the testing suite,
   and the Agent Installer. Under certain conditions, using --socket
   would fail when used with an unattended installation, or with --
   test-credentials. (Bug #17742407)

* When the service manager was unavailable, and when the HTTP threads
   were hung waiting for timeouts, the inflow of collected data could
   have exhausted the heap, which caused the Agent to run out of memory
   and shut down. (Bug #17790128)

* Text on the InnoDB Buffer Pool Usage graph was updated, and now
   reads as:

   It is not recommended to run this report on instances with large
   InnoDB buffer pools (over approximately 32 GB). Generating this data
   incurs a mutex lock for every 10,000 pages read within the buffer
   (in a loop), which can decrease throughput/concurrency of connected
   clients. If no data is returned within 2 minutes this report will
   automatically time out. (Bug #17669455, Bug #70729)

* Added a better explanation for the case when Example Query is
   enabled but example queries are not available.  For more
   information, see Section 7.1.1, "Using the MySQL Performance
   Schema". (Bug #17666148)

* The binary log related advisors now check whether binary logging is
   enabled before performing related tests. Binary log events are no
   longer generated if this feature is disabled. (Bug #17697324)

* The Upgrade Installer now checks for available disk space before
   initiating an upgrade, and halts operation if it determines that
   there is not enough. This required amount is logged as "Total
   required space: XXXXMB" in bitrock_installer.log. (Bug #17705002)

* Disabling, and then enabling an Advisor would lose the custom
   configurations that were made to the Advisor. (Bug #17670151)

* On Linux and Mac OS X, with the MySQL Enterprise Service Manager
   Installer, attempting to change the default ports to values such as
   80/443 would fail, and report an error about not being able to bind
   to ports below 1024. (Bug #17611217)

* On Solaris 10 with the Solaris Studio installed, the Installation
   would fail when attempting to use an existing MySQL Instance as the
   MySQL Enterprise Service Manager Repository Database. (Bug
   #17656476)

* User authentication failures are handled more gracefully, as
   sometimes unhandled exceptions were thrown. (Bug #17648304)

* The Bad Connections panel was improved. Error messages now show the
   actual error instead of masking them with simple titles like
   "General Error", the data of the last error was added, and now each
   error lists its own timestamp. (Bug #17632841, Bug #70670)

* The jsvc utility is now used to start/stop Apache Tomcat. It
   provides general improvements, such as timing the Apache Tomcat
   "stop" so it always removes the associated PID file. (Bug #17595732,
   Bug #70600)

* Executing config.sh without any arguments would generate a stack
   trace. (Bug #17569034)

* Unix domain sockets are now supported on Solaris SPARC systems. For
   example, --socket may now be passed to agent.sh. The required
   libjunixsocket library was missing. (Bug #17557465)

* The shutdown port, 18085, is no longer used as MySQL Enterprise
   Service Manager now uses procrun on Microsoft Windows, and jsvc on
   Mac OS X and Linux, to launch and control the Service Manager.

   Previously, 18085 was a locally bound port used by
   mysqlmonitorctl.sh to stop and start Apache Tomcat. (Bug #17559033,
   Bug #70505)

* With a large amount of assets (around 400+), the Asset Selector
   would not load, as it could reach the browser's localStorage limit.

   The lz-string library is now used to manage localStorage
   compression. (Bug #17511979)

* When there was large amount of replication topologies, adding more
   topologies would increase the CPU dramatically, and slow the
   application. (Bug #17512054)

* The --test-privileges option was added to agent.sh. It works
   similarly to --test-credentials with the exception that it only
   tests the Administrative user, and it tests both its privileges (to
   CREATE USER) and credentials. An error code of 4 is returned when
   the Administrative user is missing the CREATE USER privilege. (Bug
   #17390504)

* JDBC's StandardSocketFactory was extended to include IPv6 support.
   (Bug #13365163)

* A help tooltip was added to the Asset Selector search function. It
   notes that the search is case-insensitive, and that a search string
   must be 3+ characters in length.

* Agent replication connection credential/privilege problems are now
   only logged once as a warning, and are logged as exceptions in debug
   mode. Before it could clutter the standard logs with exceptions. For
   example, a slave requires special permission to access a master's
   UUID.

* After adding a MySQL instance to monitor with all wrong credentials,
   and editing it with the correct credentials (so it was monitored
   normally), repeating this process after removing the MySQL instance
   from being monitored would cause it to show up in the monitored
   MySQL instances table. In this case, it would show up as both
   monitored and unmonitored.

* The MySQL Enterprise Plugin for Connector/J logged the wrong version
   and build number, as it reported 1.0.0.0 instead of 1.0.0.94.

* New Advisors, which are added when MySQL Enterprise Service Manager
   is upgraded, are now auto-scheduled to start.

* When a custom collection had both delta and regular variables, the
   rule evaluation would occur for both.
Thread
MySQL Enterprise Monitor 3.0.4 Is Now Availableandy bang5 Dec