MySQL Enterprise Monitor also allows you to remotely monitor your MySQL instances in the cloud. To do this, you need to install MySQL Enterprise Monitor on your system – the good news is that you can easily do this without even needing to attend to the installation. There is also no configuration needed.
So let’s say you need to remotely monitor a relational database service instance on the cloud.
Using MySQL Enterprise Monitor, you can see the details of your RDS instance that you would want to monitor, including the end point of the RDS instance, the admin user and the security group. You will need to take note of these because you are going to need these information to add your RDS instance to MEM.
In MySQL Enterprise Monitor, you would need to go to the Instance Management section and create a group for your remote instances, including the RDS instance that you will want to monitor. Add the RDS instance that you want to monitor by inputting all the data, such as the endpoint URL, as well as the schema that you have used to create your RDS instance, as well as the group you have created for your RDS instance.
After all these, you will see that the RDS instance is already being monitored! Even a few seconds into the setup, your alerts would have already been triggered. MySQL Enterprise Monitor schedules all advisers automatically for all new instances that you add. Also, time series graphs are also automatically set up.
Monitoring your MySQL instances in the cloud has never been easier! Get MySQL Enterprise Monitor now!
[expand title=”Click here to read more about this article”]
Here’s the video demo:
Welcome! In this presentation I’ll demonstrate the cloud-friendly design in MySQL Enterprise Monitor or MEM version 3.0.
In order to demonstrate this point, I’m going to walk you through monitoring a remote RDS instance on Amazon Web Services using MEM 3.0.
First, I’m going to begin the installation of MEM and this is a simple shell script on. All I’m doing here is installing the MEM server using the unattended installation mode. I don’t need a mask of any agents. I don’t need to install or configure anything else within MEM itself and I’m just gonna go ahead and run that installer then the install takes about 60 seconds on this machine.
Oh that’s running. Let’s look at the details at the RDS instance that I’ve created for this demonstration. Here we can see the end point to the URL of my RDS instance. I’m going to copy that, as I’ll be specifying that when I set up the monitoring here shortly.
We can see the default scheme now that I’ve created with this RDS instance. It’s important that you have an existing schema that we can use for the inventory table that the MEM server will create when it begins to monitor this RDS instance of MySQLd. Now talk about why that is surely.
Here we can see the admin level user that I created for this RDS instance. A key point here is that this user does not have the typical route at the local host level privileges. This user doesn’t have the Super privilege for example. Here you can see the security group that I have assigned to it. The security group is defines that all TCP/IP traffic from the MEM server machine that I’m using is authorized. Now let’s comeback to the MEM server as that install is finished as well. We’ll complete the initial setup with this one-time setup screen.
I’ll accept the default time zone information, which is correct for me. Now we’ll go into the MySQL instance management section at the dashboard. And the first thing I’m going to do is create a group. I’ll call it AWS. And this is the group I’ll use for all my RDS instances. And now I’m gonna add an instance to be monitored. And here’s where I finally specify the connection information from our RDS instance.
First, I’ll specify the end point or URL from our RDS instance. Then for the admin user, I’ll specify that same AWS root account information that I specify when creating the RDS instance. There are two very important points that I need to make here and this is what I alluded to before. First is that you want to tell MEM not to create the secondary user accounts and simply use the admin level account for all of its connections. The reason being that the RDS admin account doesn’t have all the necessary privileges to create them as their defined in MEM. Second, you need to go into the Advanced Settings tab and change the inventory table schema for MySQL to something else – any schema that currently exists.
I’ll use the MEM schema that I created with my RDS instance. The reason for that is again at the RDS admin account doesn’t have the necessary privileges on the MySQL system schema. Finally, I’m going to specify the AWS group for this instance. Now we can see that our RDS instance is being monitored. You’ll notice that due to the various levels of DNS our instance doesn’t have a very user-friendly display name.
So I’m gonna go ahead and change that as well. I might change it to a shortened version of the RDS end-point through URL. And that’s it. Now we’re done. And if you poke around for a few seconds, we can see that we already have some alerts that I’ve triggered for this instance and that’s because MEM 3.0 automatically schedules all the advisers by default for any new instance that we monitor. And we can see that all the advisors are enabled here. And finally we can see that the time series graphs are already starting to come in as well.
So as you can see, thanks to agent-less monitoring capabilities of MEM 3.0, along with the automatic scheduling of advisers, it’s very easy to begin monitoring your MySQL instances in the cloud.
And that’s all for this video. Thank you for watching and please be sure to look for our other video demos of MEM 3.0.
Photo by MySQL.