Carrying on with my MySQL 5.7 Labs Multi Source Replication scenario, I wanted to evaluate performance impact via MySQL Enterprise Monitor.

Whilst I opened my environment, I remember that I had generated lots of different skeleton scripts that allowed me to deploy the 50 servers quickly, and I didn’t want to add each of my targets 1 by 1 in MEM. So, I used one of the many features available, “Add Bulk MySQL Instances”.

So, I’ve got 50 (3001-3050) masters but only 1 slave (3100).

By default, MEM monitors it’s own repository, i.e. the 1/1 server being monitored in the All group.

I want to add my slave in first, because that’s how I’m organizing things, and I’ll take the opportunity to create the monitoring group I want to …

At the last OOW MySQL Plugin for Oracle Enterprise Manager (OEM) was recognized as most popular MySQL product. If you don't have OEM installed, but want to test the plugin you can download OEM virtual box template. But, althought this is the easiest way to get started, you still need to make few additions. At least I had to do them when deployed such installation for MySQL Support Team.

Here they are. I prefer to use command line when possible.

0. Import virtual machine image and change network adapter to working one, then allow to connections via rdesktop:

sudo vboxmanage import VBox_EM12cR4.ova --vsys 0 --vmname  …

Once again, Geir Høydalsvik and I had the pleasure of hosting a MySQL mini-seminar in Trondheim. 25+ attendants from at least 7 different companies and a few professors from the computer science dept. at NTNU showed up on yesterdays event. I recognized many of these from the first seminar but there were some new faces as well.

This time, Mark Leith came on a visit from the UK. He gave an introduction to Performance Schema and ps_helper. ps_helper is a really nice tool to make sense of the overwhelming amount of data collected by PS. He also gave a very convincing demo of MySQL Enterprise Monitor (MEM). More than a few attendants now plan to give MEM a try in their environment. You can too - there's a 30 day trial, which should be more than enough to decide if you need it …

Time to install MEM 3.0, and get its built-in agent working.

[ If you want some tips on What's New, have a look here. ]

I’ve downloaded the Monitor Server and the agent zipped s/w for Linux & Win from http://edelivery.oracle.com:

mysqlmonitor-3.0.0.2887-linux-x86-installer.bin
mysqlmonitoragent-3.0.0.2887-linux-glibc2.3-x86-32bit-installer.bin
mysqlmonitoragent-3.0.0.2887-windows-installer.exe

The Monitor install

So, on my Oracle Linux machine:

./mysqlmonitor-3.0.0.2887-linux-x86-installer.bin

It all installs fine. No issues, if you’re used to MEM 2.3.

Double check your configuration_report.txt :

MySQL Enterprise Monitor (Version 3.0.0.2887 : 3.0.0.2887)

Here are the settings you …

Time to install MEM 3.0, and get its built-in agent working.

[ If you want some tips on What's New, have a look here. ]

I’ve downloaded the Monitor Server and the agent zipped s/w for Linux & Win from http://edelivery.oracle.com:

mysqlmonitor-3.0.0.2887-linux-x86-installer.bin
mysqlmonitoragent-3.0.0.2887-linux-glibc2.3-x86-32bit-installer.bin
mysqlmonitoragent-3.0.0.2887-windows-installer.exe

The Monitor install

So, on my Oracle Linux machine:

./mysqlmonitor-3.0.0.2887-linux-x86-installer.bin

It all installs fine. No issues, if you’re used to MEM 2.3.

Double check your configuration_report.txt :

MySQL Enterprise Monitor (Version 3.0.0.2887 : 3.0.0.2887)

Here are the settings you …

We have setup our database servers to log all slow queries > 2 seconds. This can be done by enabling below from your configuration file or via runtime using SET GLOBAL command.

Append to configuration (my.cnf) under [mysqld]

slow_query_log = on
long_query_time = 2

Using query

SET GLOBAL slow_query_log = on;
SET GLOBAL long_query_time = 2

With this current setup, we filtered all queries from our application running more than 2 seconds. This is a good way to identify slow queries and optimise them.

However, there are also queries from the MySQL Enterprise monitor that were also being logged. In this case, i found out a (2) graph metrics checking every minute for the total backup time (total_time) and total lock time (lock_time). It takes about 3-6 seconds with only about 70 records on table.

To …

In California we are always thinking about backups.   Living near an earthquake fault line makes this necessary.  For me, it is the Hayward Fault (it runs from goal post to goal post  in University of Californa Berkeley stadium).  We are strongly advised to have backup systems for water, food, and medical emergencies.  It’s necessary to monitor your food and water emergency …

MySQL Enterprise Monitor collects a huge amount of information about MySQL and the systems that it runs on. To do this, it employs an “Agent” to collect these statistics.

This can either sit locally to the database server, or on a remote host – perhaps even the same host as the Dashboard server if you decide you don’t want to distribute it to many boxes – and checks when it is local or remote, to decide whether to collect OS statistics or not. A single agent can monitor either a single or multiple instances from the same process.

Not all of the information that it can collect is fully exposed within the UI yet however (there are so many things …

I’ve had a wild ride over the past ~4.5 years, starting with MySQL AB as a “Support Engineer”, and working through to “Senior Support Engineer”, and then “Regional Support Manager, Americas” with the MySQL Support Team - truly one of the best product support teams I’ve ever known in the IT industry, even if I am biased.

I’ve always had a passion for helping people, which is why I think I did “OK” in Support. However I’ve always also had a second passion which has been bubbling away for me too - building solutions for diagnosing database issues. I started in the database world in the Oracle market, working on monitoring and management tools. MySQL “poached” me from there whilst I was building a MySQL monitoring module for the cross database monitoring tool that we had, as well as working in a supporting/consulting role for our customers.

Given my background when I joined, I was an obvious person to be …

MySQL Enterprise Monitor offers a tool called "Query Analyzer" (QuAn). QuAn sits between any client app and the MySQL server and logs every query and its runtime statistics. A very cool tool for analyzing your SQL. More information is available here.If you identify a query, that needs some improvement, sometimes it is hard to identify the source of that query as well. With hundreds of different PHP scripts for example it is not easy to know, which one issued the query, that you want to modify.A good way to achieve this is adding C-style SQL comments. Let's look at an example: SELECT * FROM mytable …