MySQL Enterprise Monitor is available as part of the MySQL Enterprise subscription, learn more at http://www.mysql.com/products/.
How do I find
Ignored MySQL Instances? And
how to I show them again?
In 2.3, the
agent-mgmt-hostname contained the
string "heartbeat" as the URLs path. Did this change?
A.3: How do I change the name of a server?
A.4: Why do some rules appear to have a Severity of Unknown?
A.5: Can I run MySQL Enterprise Service Manager on machine with other applications running?
Why does the file
apache-tomcat/logs/tomcat.log show error
This is very likely to create a memory
leak.? Is that anything to be concerned about?
A.7: Why does monitoring a MySQL instance with FEDERATED tables cause extra connections, and decreased performance?
Questions and Answers
From the MySQL
Instances page, open the search panel and change the
Ignored Instance filter parameter to
Enabled, and then execute the search. This
lists the ignored MySQL Instances.
To change the status of an ignored MySQL Instance, choose Show Instance from the context-menu for a specific MySQL Instance, or check the ignored MySQL Instance(s) and click the Show Instances button.
Yes, this is no longer required and is ignored as of MySQL Enterprise Monitor 3.0.0.
Go to Monitor, MySQL Instances, and choose Edit Instance after hovering over the instance you want to rename. Alternatively, you may toggle the checkbox for one instance and click Edit Instances.
Renaming the server in this way will override all other server naming, including changes to the agent configuration.
Due to timing issues, certain rules such as “32-Bit Binary Running on 64-Bit AMD Or Intel System” and “Key Buffer Size Greater Than 4 GB” do not evaluate correctly due to timing issues. This is a known issue that is expected to be resolved in future versions of MySQL Enterprise Monitor.
You can, but Oracle recommends running your MySQL Enterprise Service Manager on a dedicated machine, especially when monitoring many agents.
This message is sometimes produced by underlying components of the web stack on web application reload or shutdown, and is not a cause for concern. It is not practical to shut off these spurious messages within Tomcat.
When the agent starts, it executes a discovery process that performs a number of INFORMATION_SCHEMA queries that gather table information for rules. These INFORMATION_SCHEMA queries can be costly on instances with many tables, particularly with large numbers of FEDERATED tables to another instance, as each table has a new session opened for it on the target machine.
If you do not want these statements to execute on agent startup,
any statement relating to the INFORMATION_SCHEMA can be removed
from the agent's
file. However, this will cause some of the rules provided with
your subscription to not work, as they rely on this information.
A.1: What is MySQL Enterprise Monitor?
A.2: What are the features and related benefits of the MySQL Enterprise Monitor?
A.3: What are the immediate benefits of implementing the MySQL Enterprise Monitor?
A.4: What are the long-term benefits of the MySQL Enterprise Monitor?
A.5: How is the MySQL Enterprise Monitor installed and deployed?
A.6: How is the Enterprise Monitor web application architected?
A.7: What makes MySQL Enterprise unique?
A.8: What versions of MySQL are supported by the MySQL Enterprise Monitor?
A.9: What operating system platforms are supported by the MySQL Enterprise Monitor?
A.10: What are the MySQL Enterprise Monitor Advisors?
A.11: How are subscribers notified about the availability of new or updated MySQL Enterprise Monitor, MySQL Enterprise Advisors and Advisor Rules?
Questions and Answers
Included as part of a MySQL Enterprise subscription, the MySQL Enterprise Monitor is a distributed, web-based application that helps customers reduce downtime, tighten security and increase throughput of their MySQL servers by telling them about problems in their database applications before they occur. It is downloadable from the Oracle Software Delivery Cloud web site and is deployed within the safety of the customer data center.
The MySQL Enterprise Monitor is like having a "Virtual DBA Assistant" at your side to recommend best practices to eliminate security vulnerabilities, improve replication, and optimize performance. For the complete features and benefits, visit the http://www.mysql.com/products/enterprise/monitor-features.html.
Often MySQL installations are implemented with default settings that may not be best suited for specific applications or usage patterns. The MySQL Advisors go to work immediately in these environments to identify potential problems and proactively notify and advise DBAs on key MySQL settings that can be tuned to improve availability, tighten security, and increase the throughput of their existing MySQL servers
Over time, the task of managing even medium-scale MySQL server farms becomes exponentially more complicated, especially as the load of users, connections, application queries, and objects on each MySQL server increases. The Enterprise Monitor continually monitors the dynamic security, performance, replication and schema relevant metrics of all MySQL servers, so as the number of MySQL continues to grow, DBAs are kept up to date on potential problems and proactive measures that can be implemented to ensure each server continues to operate at the highest levels of security, performance and reliability.
The Enterprise Monitor is powered by a distributed web application that is installed and deployed within the confines of the corporate firewall.
The Enterprise Monitor web application comprises three components:
Monitor Agent: A lightweight Java program that is installed on each of the monitored hosts. Its purpose is to collect MySQL SQL and operating system metrics that allow the DBA to monitor the overall health, availability and performance of the MySQL server and host. The Monitor Agent is the only component within the application that touches or connects to the MySQL Server. It reports the data it collects via XML over HTTP to the centralized Service Manager.
Service Manager: The main server of the application. The Service Manager manages and stores the data collections that come in from each monitor agent. It analyzes these collections using MySQL provided best practice Advisor rules to determine the health, security, availability and performance of each of the monitored MySQL Servers. The Service Manager also provides the content for the Enterprise User Interface which serves as the client user interface for the distributed web application.
Repository: A MySQL database that is used to stored data collections and application-level configuration data.
Of the products on the market that monitor MySQL, SQL code and OS specific metrics, the MySQL Enterprise Monitor is the only solution that is built and supported by the engineers at MySQL. Unlike other solutions that report on raw MySQL and OS level metrics, the MySQL Enterprise Monitor is designed to optimize the use of MySQL by proactively monitoring MySQL instances and providing notifications and 'MySQL DBA expertise in a box' advice on corrective measures DBAs can take before problems occur.
The MySQL Enterprise Monitor supports MySQL versions 5.1 and above.
The Enterprise Monitor Service Manager is fully supported on most current versions of Linux, Windows and Windows Server Editions, Solaris and Mac OS X. The Monitor Agent supports any platform supported by the MySQL Enterprise server. For the complete list of MySQL Enterprise supported operating systems and CPUs, visit the http://www.mysql.com/support/supportedplatforms/database.html.
Advisors filter and evaluate the information broadcast by the Monitoring Agents and present it to the Events page when defined thresholds are breached. They also present advice on how to correct the issue. There are more than 200 Advisors, all of which are enabled by default. Thresholds are the predefined limits for Advisors. If the monitored data breaches the defined threshold, an event is generated and displayed on the Events page. Advisor thresholds use a variety of different value types, depending on the monitored value. Some use percentages, such as percentage of maximum number of connections. Others use timed durations, such as the average statement execution time. It is also possible to check if specific configuration elements are present or correct.
Customers will receive notifications of new and updated MySQL Enterprise Monitor and Advisors as they become available via the MySQL Enterprise Software Update Service. Notifications will be generated and sent based on the customer profile and the MySQL Enterprise subscription level.
A.1: What is the MySQL Query Analyzer?
A.2: How is the MySQL Query Analyzer installed and enabled?
A.3: What are the main features and benefits of the MySQL Query Analyzer?
A.4: What are the typical use cases of the MySQL Query Analyzer?
A.5: What makes the MySQL Query Analyzer unique?
A.6: How can I get the MySQL Query Analyzer?
A.7: Does Query Analyzer work with MySQL Cluster?
A.8: Does Query Analyzer capture queries by the root user?
A.9: Does Query Analyzer enable me to monitor the disk reads and writes during a query?
A.10: Does the "Rows" area show the rows returned/updated or the rows visited by the query?
A.11: Will the Query Analyzer work without any special setup?
Questions and Answers
The MySQL Query Analyzer allows DBAs, developers and system administrators to improve application performance by collecting, monitoring, and analyzing queries as they run on their MySQL servers. http://www.mysql.com/products/enterprise/query.html
For the complete features and benefits, visit the http://www.mysql.com/products/enterprise/monitor-features.html
The typical use cases for developers, DBAs and system administrators are:
Developers – Monitor and tune application queries during development before they are promoted to production.
DBAs and System Administrators – Identify problem SQL code as it runs in production and advise development teams on how to tune. This use case benefits the most from regular sampling of queries as they are running, most often during non-peak hours.
Other products (free, open source and commercial) that provide MySQL query monitoring are dependent on the MySQL Slow Query Log being enabled and available for sampling. While this provides some time savings over the DBA collecting and parsing the Log, the Slow Query Log comes with overhead and does not capture sub millisecond executions. The log data also grows very large very quickly.
The MySQL Query Analyzer collects queries and execution statistics with no dependence on the SQL Query Log, it captures all SQL statements sent to the MySQL server and provides an aggregated view into the most expensive queries in number of executions and total execution time. It is also fully supported as part of the MySQL Enterprise subscription.
The MySQL Query Analyzer is built into the MySQL Enterprise Monitor.
To experience the MySQL Enterprise Monitor for 30 days, visit the http://www.mysql.com/trials/
Yes, providing that exact node is monitored with an agent and query analyzer has been enabled for that node. Note that you must be accessing your cluster data through a standard MySQL node for this to work.
Yes, Query Analyzer captures all queries by all users providing that the queries are sent through the proxy port configured by the MySQL Enterprise Monitor Agent.
No, that information is not available to the query analyzer, but many Advisors and graphs do handle this information. An Agent monitors the host, which includes monitoring of the CPU, Disk, and Memory.
Returned/updated. We don't have visibility into how many rows were touched. at an instance level. Some of the graphs we provide will show you when you're queries are touching a lot of rows.
With MySQL Server 5.6.14 and greater, Query Analyzer data is automatically (by default) collected and displayed using the Performance Schema Statement Digests MySQL Server (Performance Schema Statement Digests) feature. If you are monitoring an earlier MySQL Server version, then you can continue to use alternative methods of providing query data to the Query Analyzer.
For information about the different methods of retrieving query data, see Section 23.1, “Providing Query Analyzer Data”.