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 …

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 …

Ok, so after all the things that have been announced @MySQLConnect, I’ve got to play around with them. First stop: space (no.. not ‘the final frontier’).

I need more space on my f/s to get installing. I was a bit of a scrooge when I created my Oracle Linux virtual machine, so now I’m paying the price.

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_ol63uek01-LogVol01
                      7.1G  5.7G  1.1G  85% /

As I’m using Virtual Box, I’ve added a new SATA Controller vmdk of 10G, SATA Port 1 and then start it up.

fdisk -l

Will be able to identify the new & unused partition:

[root@ol63uek01 ~]# fdisk -l
Disk /dev/sda: 8589 MB, 8589934592 bytes
 255 heads, 63 sectors/track, 1044 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: …

Ok, so after all the things that have been announced @MySQLConnect, I’ve got to play around with them. First stop: space (no.. not ‘the final frontier’).

I need more space on my f/s to get installing. I was a bit of a scrooge when I created my Oracle Linux virtual machine, so now I’m paying the price.

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_ol63uek01-LogVol01
                      7.1G  5.7G  1.1G  85% /

As I’m using Virtual Box, I’ve added a new SATA Controller vmdk of 10G, SATA Port 1 and then start it up.

fdisk -l

Will be able to identify the new & unused partition:

[root@ol63uek01 ~]# fdisk -l
Disk /dev/sda: 8589 MB, 8589934592 bytes
 255 heads, 63 sectors/track, 1044 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: …