MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:john.russell Date:November 18 2010 9:40pm
Subject:svn commit - mysqldoc@docsrva: r23842 - trunk/dynamic-docs/changelog
View as plain text  
Author: jrussell
Date: 2010-11-18 22:40:54 +0100 (Thu, 18 Nov 2010)
New Revision: 23842

Log:
Copying over new changelog file with 2.3-era updates.


Added:
   trunk/dynamic-docs/changelog/monitor-1.xml


Added: trunk/dynamic-docs/changelog/monitor-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/monitor-1.xml	                        (rev 0)
+++ trunk/dynamic-docs/changelog/monitor-1.xml	2010-11-18 21:40:54 UTC (rev 23842)
Changed blocks: 1, Lines Added: 2868, Lines Deleted: 0; 56851 bytes

@@ -0,0 +1,2868 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE changelog PUBLIC "http://dev.mysql.com/doc/dtd" "http://dev.mysql.com/doc/dtd/changelog.dtd"
+[
+<!ENTITY % all.entities SYSTEM "all-entities.ent">
+%all.entities;
+]>
+<changelog>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			Query Analyzer, Replication monitoring, and all rules and graphs are now available to all licensed users.
+			See <ulink url="http://www.mysql.com/products/"/> for details.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			There is no longer a requirement to enter a license key.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			The <quote>What's New?</quote> page integrates with My Oracle Support service, in addition to the MySQL Enterprise web site.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			There is a new advisor and corresponding graph for MySQL Cluster.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			There is a new advisor and corresponding graph for InnoDB Plugin.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			There is a new advisor and corresponding graph for
+			network and disk I/O.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+			The new Aggregator component accepts Query Analyzer data from any source.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="55949"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The embedded OpenSSL has been updated to version 0.9.8o.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54533"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The supplied <command>setenv.sh</command> script sets the wrong
+        temporary directory value for <literal>HeapDumpPath</literal>.
+        The path has been updated to the
+        <filename>monitor/apache-tomcat/temp</filename> directory within
+        the &merlin_server; installation.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="56192"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When performing an unattended installation, the &merlin_server;
+        would not be restarted automatically if the configuration file
+        contained changes. You can now force the restart to occur by
+        using the <literal>--forceRestart</literal> option. When set to
+        1, the server will be restarted using the old (unmodified)
+        configuration file.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="55516"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When the MySQL server supporting &merlin_server; is unavailable,
+        the <filename>catalina.out</filename> file is populated with
+        error messages for each &merlin_agent; communicating with
+        &merlin_server;. The quantity and frequency of the messages can
+        cause the error log to grow at a very fast rate. The logging
+        configuration has been altered so that Tomcat-specific errors go
+        to <literal>tomcat.log</literal>, rotating every 10MB for up to
+        10 logs. Application errors are reported in
+        <filename>mysql-monitor.log</filename>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="56004"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <literal>--skip-locking</literal> option for the embedded
+        MySQL server was being used in place of the deprecated
+        <literal>--skip-external-locking</literal> option.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="security"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="55585"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        It was possible for a user without the ability to view the
+        <guilabel>Manage Users</guilabel> page by visiting the URL, even
+        if the user was not authorized to view the page. Users without
+        the right credentials are now provided with a warning that the
+        page is unavailable.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="security"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="56189"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The content of the user field on the <guilabel>Edit
+        User</guilabel> screen was not protected so it was possible to
+        insert scripting instructions into the field contents.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="security"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="56187"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        It was possible to fake the request and promote a user to a
+        different role without having the privileges to do so.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52985"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The Tomcat <filename>config.properties</filename> file could be
+        installed with unsafe permissions.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="55450"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Using LDAP authentication for mapping roles using user
+        attributes would not authenticate correctly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="55453"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The same example query could be consistently resent to
+        &merlin_server;, even though the example query had already been
+        reported.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52933"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <literal>GRANT</literal> for the <literal>agent</literal>
+        user could include permissions for a wide range ofd hosts, and
+        different grant sould be created by different platform
+        installers.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="35203"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The file permissions on the <filename>mysql</filename> directory
+        within the &merlin_server; installation would not be set
+        correctly on Mac OS X.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53943"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.3"/>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The &merlin_agent; installer would ask for agent credentials,
+        even if you had indicated that the correct user credentials had
+        already been created.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54002"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A &merlin_agent; could report the a MySQL instance as being
+        down, even though the instance was available. This was related
+        to the way local and remote filesystems were identified and
+        reported by &merlin_agent;. A new option,
+        <option>--agent-report-network-fs</option> has been added to
+        indicate whether remote filesystems should be reported in the
+        diskspace reports. By default, the &merlin_agent; no longer
+        reports network filesystem information, only data for local
+        filesystems.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54618"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The data reported for the binary log file size (in
+        <literal>mysql::masterlogs::filesizesum</literal>) was
+        erroneously reporting the count of the files, not the sum of the
+        size of the binary logs.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="41168"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Errors determining <literal>InnoDB</literal> data within
+        &merlin_agent; would be reported, even when
+        <literal>InnoDB</literal> had been disabled on the instance.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="44748"/>
+      <fixes bugid="47374"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When reporting errors related to multiple instances monitored by
+        the same &merlin_agent;, the error message would not indicate
+        which instance reported the error.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54806"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        LDAP roles using the search method did not work when searching
+        for authentication credentials.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54047"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Using the <literal>Error</literal> option for the Referral
+        method for LDAP settings generates an error trace.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54136"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Using the diagnostic zip functionality would fail if you had
+        configured a server group with a forward slash
+        <literal>/</literal> in the name.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="44772"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A <literal>TRUNCATE TABLE</literal> statement could be
+        mis-identified in the tokenizer.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="50604"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message ver="2.2.0">
+
+      <para>
+        To aid in the replication discovery performed by the agent, you
+        can now provide alternative credentials for connecting to the
+        replication master to obtain the master UUID created by
+        &merlin;. The master UUID enables &merlin_agent; to more easily
+        identify and reconcile the master. You set these options on an
+        instance basis, and setting the options prevents the agent using
+        the <filename>master.info</filename> to determine the master
+        UUID.
+      </para>
+
+    </message>
+
+    <message ver="2.2.1">
+
+      <para>
+        The methods for replication discovery by &merlin_agent; have
+        been modified. A new option for &merlin_agent; has been added
+        that prevents the master UUID being used in the replication
+        topology determination. This also prevents &merlin_agent; from
+        obtaining replication information from the
+        <filename>master.info</filename> file.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54600"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The list of active support issues on the <guilabel>What's
+        New</guilabel> page has been updated to not show issues that are
+        stale, and to not show issues if you have disabled the support
+        issue checks.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54701"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The output from &merlin_agent; using
+        <literal>--version</literal> would show incorrect versions for
+        some components.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52952"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If a &merlin_agent; got a timeout during the initial checkin
+        with &merlin_server; (for instance, if &merlin_server; was
+        busy), it would fail to resynchronize properly and show the
+        monitored MySQL instances as down.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54591"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Monitoring a database with a large number of tables would lead
+        to long queries on <literal>INFORMATION_SCHEMA</literal> which
+        could lead to operating system memory graphs not being updated
+        correctly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53845"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Query Analyzer could fail to operate correctly when upgrading
+        from &merlin_server; 2.1 to &merlin_server; 2.2. Accessing the
+        details of a query could lead to a
+        <literal>NullPointerException</literal> error.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52770"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        During and upgrade installation from 2.1 to 2.2, some files in
+        the &merlin_agent; installation directory would remain. During
+        an upgrade, the installer now performs the following operations:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            The file <filename>custom.xml</filename> will be copied from
+            <filename>share/mysql-proxy/items</filename> to
+            <filename>share/mysql-monitor-agent/items</filename>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            The contents of <filename>share/mysql-proxy</filename> and
+            the directory are deleted.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            The <literal>README</literal> files in
+            <filename>share/doc</filename> are removed. The 2.2 files
+            are located in
+            <filename>share/doc/mysql-monitor-agent</filename>.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52129"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The installer dialog for the text installation for
+        &merlin_agent; would show a blank password prompt when asking
+        for confirmation of the root password.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54559"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The help output from &merlin_agent; could show missing or
+        corrupt characters.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="54433"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The &merlin_agent; could fail to start on 64-bit platforms.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53880"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        On Windows platforms, the &merlin_agent; could show increasing
+        memory usage over time.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="47676"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When performing an upgrade, the value of
+        <option>agent-host-id</option> would not be preserved.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53977"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The ssh fingerprint used to identify agents would fail on Ubuntu
+        Linux.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52280"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.3.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The timeout for information being supplied through the
+        aggregator was too high, leading to a failure to identify that
+        the aggregator was unavailable.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53090"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When <command>mysqld</command> is in a hung state and
+        unresponsive, &merlin_agent; and &merlin_server; may not report
+        the server as unavailable.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53679"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The default settings for the LDAP interface for authenticating
+        users has been updated. By default, lookups are made using
+        <literal>Bind as user</literal>, and the default password digest
+        mechanism is now MD5.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52213"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When installing &merlin_server;, the incorrect permissions could
+        be applied to the embedded MySQL server.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52198"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When performing an installation of &merlin_server; or
+        &merlin_agent; and specifying an alternative service name during
+        installation, the installer would recommend using the generic,
+        not custom, service management script to initiate the service.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52190"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Adding a new instance to the list of monitored instances while
+        using the &merlin_client; could lead to a scheduling exception
+        error.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53953"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The required version for running a separate MySQL server has
+        been updated to 5.1.43 in the &merlin_server; installer.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53425"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The filters for <literal>LOAD DATA INFILE</literal>,
+        <literal>START TRANSACTION</literal>, and <literal>HANDLER
+        CLOSE</literal> statements in the Query Analyzer interface did
+        not filter statements correctly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="47775"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When upgrading an installation of &merlin_server; where the
+        MySQL being used is not the bundled MySQL server, the upgrade
+        would fail while creating a backup of the MySQL installation.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="27332"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When performing an installation of &merlin_agent;, installing
+        multiple agents could lead to service names (Windows) and
+        startup scripts (Unix) being overwritten, corrupted, or creating
+        multiple entries. The installer will now ask for a different
+        service name, or you can explicitly specify one to the installer
+        using the <option>servicename</option> option. See
+        <link linkend="option_mysql-monitor-agent-installer_servicename"><option>installer_servicename</option></link>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52142"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Deleting a user while the user is currently logged in and using
+        &merlin_client; would not prevent the user from continuing to
+        use the &merlin_client;, even though the user no longer existed
+        in the system.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53826"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        It was possible to import a custom advisor bundle to replace the
+        main advisor bundle. This would delete all existing rules,
+        schedules and advisors. The system now checks the bundle before
+        import.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53584"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When generating a support report, the server provided no
+        feedback on the production process. A page will now be generated
+        to advise you of the current status before providing you with a
+        completed message once the report generation has been completed.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="41630"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The installer for &merlin_agent; has been updated to include
+        support for creating the username and password required by the
+        &merlin_agent; during operation. This process creates the user
+        with the necessary privileges within your monitored MySQL
+        server. For more information, see
+        <xref linkend="mem-agent-rights"/>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="38897"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If the backend MySQL database being used for &merlin_server; is
+        unavailable during an update installation, the installer may
+        give a misleading message indicating the problem.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53158"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When upgrading an existing &merlin_server; installation, where
+        the MySQL database is identified as not being on the current
+        host (either because it is on the same machine with a different
+        IP, or a different machine), the upgrade installer would fail to
+        provide a warning that such a MySQL database installation cannot
+        be upgraded automatically by the installer. A warning providing
+        more information on how to upgrade is now provided.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53557"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If the backend MySQL database being used for &merlin_server; is
+        unavailable during an update installation, the installer may
+        give a misleading message indicating the problem.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="41643"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The Query Analyzer interface has been improved to show more
+        information about query states and for the filtering system to
+        enable you to view and filter the contents to more easily
+        identify problem queries. For more information, see
+        <xref linkend="mem-query-analyzer-filtering"/>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52846"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Uninstalling &merlin_server; using the Uninstall Services tool,
+        or later removing &merlin_server; after servers have already
+        been successfully removed, could fail.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="47165"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        &merlin_agent; would fail to monitor MySQL servers using the
+        InfoBright storage engine.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53193"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A warning is now provided before generating the support
+        diagnostics information to indicate the potential time delay.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="53564"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The Query Analyzer now includes a
+        <literal>Transactional</literal> filter to cover all transaction
+        related statements, in addition to the individual statement
+        filters for <literal>BEGIN</literal>, <literal>START</literal>,
+        <literal>COMMIT</literal>, <literal>ROLLBACK</literal>,
+        <literal>SAVEPOINT</literal>, and <literal>RELEASE</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="28529"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If a Heat Chart rule had de-escalated and the corresponding
+        higher event had not been closed, the Heat Chart dot link did
+        not show the event on the Events tab. This was because the
+        de-escalated state was shown in the Heat Chart, but an Event was
+        not generated for it until the more serious Event was closed.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53419"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A <literal>LOAD DATA INFILE</literal> statement would not get
+        normalized correctly within the Query Analyzer display.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="51864"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Using <literal>LOAD DATA LOCAL INFILE</literal> would cause the
+        proxy component of &merlin_agent; to terminate.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52847"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        During installation of &merlin_server; on Windows, a batch file
+        was created to obtain the MySQL version number. This file could
+        contain security credentials for accessing the server. The batch
+        file is no longer created.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53317"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If there are directories located within the configuration
+        instances directory that are empty (i.e. contain no instance
+        configuration file), &merlin_agent; would fail to start. The
+        behavior has been updated to provide a
+        <literal>message</literal> level error.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="43051"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Starting the &merlin_agent; would prevent the current session
+        for logging out while the agent was still running.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="34240"/>
+      <fixes bugid="23640"/>
+      <fixes bugid="27132"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When events have been raised by &merlin;, new events of the same
+        type would not be notified until the original event had been
+        acknowledged. This could lead to critical events being missed.
+        In addition, when viewing existing events that have been
+        triggered, it is impossible to know if the notified event is
+        still causing a problem.
+      </para>
+
+      <para>
+        The fix has been rectified through the implementation of the
+        auto-close feature on events. With this feature enabled, events
+        will automatically be closed once the event is not longer
+        identified as causing a problem.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52800"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The filter selection in the drop down menus in the
+        <guilabel>Manage Servers</guilabel> tab have been changed from
+        blank entries (indicating all items), to
+        <literal>(all)</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="49699"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If the <literal>agent-host-id</literal> value contained a
+        period, information would fail to be reported to
+        &merlin_server;.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="53199"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The full agent URL would be output in the logs in the event of
+        an error, including the agent username and password used to
+        connect to &merlin_server;. The password is now stripped from
+        the reported URL.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="43537"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The IP address of the URL used to communicate with
+        &merlin_server; would be resolved only during initial startup by
+        an individual &merlin_agent;. This causes problems where the
+        &merlin_server; is on a virtual IP address and the DNS is used
+        to provide failure to a new IP address. IP address caching has
+        now been disabled, which should cause the IP address to be
+        re-looked up and updated during a failover of the
+        &merlin_server;.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="49739"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The memory footprint of &merlin_agent; would slowly increase
+        over time, particularly on Mac OS X and Solaris/OpenSolaris.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="50365"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The MyISAM Key Buffer Usage Graph could report misleading
+        information about the key buffer block usage allocation.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="47181"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Occasional Null Pointer Exception errors could be raised after
+        an initial login to the dashboard due to problems determining
+        the correct name to use for displaying the list of servers.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="52532"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal>EXPLAIN</literal> output within the Query Analyzer data
+        would not be rendered correctly if some of the returned
+        <literal>EXPLAIN</literal> plan data contained
+        <literal>NULL</literal> values.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48714"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The version information output for the &merlin_agent; did not
+        include the version of the all the individual components loaded
+        into the &merlin_agent; chassis.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="50806"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+      <version ver="2.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When using the &merlin_proxy;, if the backend MySQL server went
+        down, and then the clock on the &merlin_proxy; host went back in
+        time (for example, during daylight savings time adjustments),
+        the &merlin_proxy; would stop sending queries to the configured
+        backend.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="44262"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When a &merlin_agent; is disconnected from &merlin_server;, the
+        agent would keep 10 minutes of information by default, that
+        would then be sent to the server when the agent reconnected. Any
+        data older than 10 minutes would be lost. You can now configure
+        the backlog timeout by using the
+        <option>agent-backlog-timeout</option> to specify the amount of
+        time that data will be kept. For more information, see
+        <link linkend="option_mysql-monitor-agent_agent-backlog-timeout"><option>agent-backlog-timeout</option></link>
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="45683"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When viewing queries within the Query Analyzer, the example
+        query shown could be taken from outside of the time range
+        configured within the query analyzer view.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="46438"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Some queries would show multiple tables in the <guilabel>Example
+        Query</guilabel> displayed within the Query Analyzer.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="41005"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When running an update installation on a machine where you have
+        multiple instances of &merlin_agent; already installed, the
+        installer could identify and upgrade the wrong version. You can
+        now specify the installed version (as identified by the startup
+        script in <filename>/etc/init.d</filename>) by using the
+        <literal>--servicename=<replaceable>mysql-monitor-agent</replaceable></literal>
+        option to the command line installer.
+      </para>
+
+      <para>
+        For new installations where a instance of the &merlin_agent; is
+        already installed, the installer could identify an existing
+        version and refuse to perform the installation process. During
+        the installation, you are now prompted with the installation
+        name to use for the startup script if, and only if, an existing
+        instance has been identified.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="49407"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The &merlin_client; has been confirmed as compatible with Google
+        Chrome 4.0.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="48329"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <guilabel>Manage Servers</guilabel> window has been updated
+        to allow you to view and filter the list of servers using a
+        variety of criteria, making it easier to find servers, agents,
+        or both that require upgrading.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="50259"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        You can delete multiple servers from the Manage Servers tab by
+        selecting each server and using the <guibutton>delete
+        servers</guibutton> button.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="41076"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When viewing detailed query information within the query
+        analyzer, the incorrect 'worst' query could be shown in the
+        detail view.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="40823"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When hovering over the heat chart, you now get a count of the
+        number of servers affected by the corresponding rule within the
+        tooltips, even when the list of servers, or specific server
+        groups, are collapsed.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="51218"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Creating a new custom rule without a configured variable would
+        not raise an error. The system will now return <literal>U0068
+        One or more variables is required to make a functioning
+        rule.</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="46667"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The schedule for the <guilabel>MySQL Agent Not
+        Reachable</guilabel> rule cannot be modified. This is to ensure
+        that problems communicating with the agent are identified
+        immediately. If you attempt to modify the scheduling an error
+        will be reported.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="47877"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When adding a new rule without providing a version a stacktrace
+        would be produced. A default version (<literal>1.0</literal>)
+        will be added to new rules if the version has not been
+        specified.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="51118"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        During an upgrade installation of &merlin_server;, custom SSL
+        certificates that had been installed could be replaced by the
+        standard versions. Existing custom certificates are now
+        preserved during an upgrade.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48581"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When upgrading an agent, the existing agent is shutdown and then
+        restarted after the installation process has completed. To
+        reduce downtime during installation, you can now opt to have the
+        agent restarted immediately after installation, but before the
+        rest of the installer completes.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="50340"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When the agent is shut down, the message used to be reported at
+        the <literal>critical</literal> log level. This has been changed
+        so that shutdown message are now reported at the
+        <literal>message</literal> log level. You can enforce the
+        shutdown message to be reported in the log regardless of the log
+        level by using the <literal>verbose-shutdown</literal> option.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48479"/>
+      <fixes bugid="50121"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Cutting and pasting sample queries from Query Analyzer page in
+        could lead to bad concatenation of the query components.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="40729"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In the event of a failure by &merlin_agent; to communicate with
+        the &merlin_server;, for example when the server has been
+        restarted, it was possible for there to be gaps in the reported
+        information. This may have shown up as gaps in the graph output.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="50881"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        If the MySQL server holding the repository information for
+        &merlin_server; crashes and you are using MySQL Proxy to monitor
+        the backend server, the problem may be difficult to identify
+        from the logs.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="49626"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When starting up MySQL Enterprise Monitor, the relevant
+        environment variables are now inserted into the
+        <filename>catalina.out</filename> log duing startup.
+      </para>
+
+      <para>
+        The environment variables reported include:
+      </para>
+
+<programlisting>
+$CATALINA_BASE
+$CATALINA_HOME
+$CATALINA_TMPDIR
+$JAVA_HOME
+$JRE_HOME
+$_RUNJAVA
+$JAVA_OPTS
+$CATALINA_OPTS
+$JAVA_ENDORSED_DIRS
+$CLASSPATH
+</programlisting>
+
+      <para>
+        In addition, the version information for the Java environment
+        used will also be reported in the log.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="46436"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        On very large deployments with a large number of servers, the
+        <guilabel>Events</guilabel> tab could take some time to load.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="50347"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The included Java runtime environment has been updated to JDK
+        6.0 Update 18.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="49471"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The information in the table on the <guilabel>Query
+        Analyzer</guilabel> page was displayed in either ascending sort
+        order, descending sort order, or an unsorted order. You could
+        change this behavior by clicking the column you wanted to sort.
+      </para>
+
+      <para>
+        The behavior has now been modified so that the table data is
+        sorted in either ascending or descending order, clicking the
+        columns toggles between these two states.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <bugs>
+      <fixes bugid="45436"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Custom graphs and advisors can now be imported, exported and
+        deleted from the system. See
+        <xref linkend="mem-settings-import"/>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="47802"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The indentation on alert emails could be incorrect if the list
+        included a bullet list of items.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="49306"/>
+      <fixes bugid="49903"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The method for generating a new UUID for the &merlin_agent; has
+        been changed. You can create a new UUID using:
+      </para>
+
+<programlisting>shell&gt; bin/mysql-proxy --plugins=agent --agent-generate-uuid</programlisting>
+
+      <para>
+        Alternatively, you can use the
+        <command>bin/agent-generate-uuid</command> command in the agent
+        installation directory.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="26167"/>
+      <fixes bugid="35278"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Different Advisor jar and subscription levels could be installed
+        at the same time, which could lead to incompatibilities and
+        scheduling issues. In addition, you could install different
+        Advisor jar files and corrupt the localization descriptions for
+        the advisors.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="49769"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The <filename>configuration_report.txt</filename> file would
+        cont6ain information about the SSL port to use, even if SSL
+        support had not been enabled during installation.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48255"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Deleting a server or group from the <guilabel>Manage
+        Servers</guilabel> tab could result in a stacktrace dump if the
+        server or group ID selected was no longer valid. A confirmation
+        is now produced if &merlin_server; identifies an issue when
+        trying delete the selected server or group.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="36885"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The formatted query view in the pop-up within the
+        <guilabel>Query Analyzer</guilabel> tab could show an empty
+        query if the query was short and could not be formatted
+        properly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48408"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Changing the filter parameters on the <guilabel>Query
+        Analyzer</guilabel> tab would lose your current sorting
+        preferences.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="46604"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Pressing cancel on a pop-up would cause a page reload, instead
+        of just closing the pop-up window.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="39457"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        It was not possible to order the rows in the table within the
+        <guilabel>Manage Servers</guilabel> tab. You can now sort by
+        clicking the required column.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48409"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When viewing pages of queries on the <guilabel>Query
+        Analyzer</guilabel> tab, changing the filter options could lead
+        to an empty list if you modified the filters while on a page
+        that is higher than the number of the pages in the filtered
+        display. The page numbering is now reset when you change the
+        filter options to ensure that you are viewing the filtered
+        queries.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48390"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When viewing the <guilabel>Query Analyzer</guilabel> tab and
+        selecting a server, the server name would still shown in the
+        table of queries. When a server has been explicitly selected,
+        the server column is no longer displayed.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48713"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When using the proxy (for query analyzer) with the
+        &merlin_agent;, the <literal>proxy</literal> plugin must be
+        listed first in the <literal>plugins</literal> configuration
+        parameter.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48712"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The name of the section in
+        <filename>mysql-monitor-agent.ini</filename> required for
+        configuration is <literal>mysql-proxy</literal>, the default
+        template had been mistakenly modified to
+        <literal>mysql-monitor-agent</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48718"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The backend Lua scripts used with the MySQL Proxy and
+        &merlin_agent; were not updated for the the MySQL Proxy 0.8.0
+        core. This would lead to some Lua scripts triggering an error.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="48193"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+      <version ver="2.1.1"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The URL for viewing the contents of an event alerted by email
+        were not populated correctly, making the supplied URL invalid.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="42688"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Queries containing <literal>DATE_SUB</literal> functions could
+        show incorrect queries when normalized within Query Analyzer.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="40676"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Queries containing an <literal>INNER JOIN</literal> clause could
+        show incorrect queries when normalized within Query Analyzer.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="38892"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.2.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Queries containing an <literal>LIMIT</literal> clause with value
+        placeholders could show incorrect queries when normalized within
+        Query Analyzer.
+      </para>
+
+    </message>
+
+  </logentry>
+
+</changelog>


Thread
svn commit - mysqldoc@docsrva: r23842 - trunk/dynamic-docs/changelogjohn.russell18 Nov