One of the reasons why you should use MySQL Enterprise Monitor is that it allows you to track the performance and health of your MySQL servers and how easy it is to do so.
Once you log into your MySQL Enterprise Monitor, you will see the overview screen where you could get a quick view of your entire monitored infrastructure. So it is very easy to check on the overall health of everything you are monitoring.
Alternately, you can just select a certain group that you are concerned with.
For example, you can select the production replication group and see:
- That group’s long-term availability
- What servers are included in this group
- How many connections are handled by the group
- The general database activity including select, updates, insert, replace, delete and call statements
- The average query response times
- Problematic MySQL instances, or those that are not running or have critical alerts
- Problematic host machines, and
- The list of unhandled critical events in your group
My SQL Enterprise Monitor allows you to get all of these information in just one screen, making the overview screen a great, convenient and easy way to monitor the health of your assets.
Here’s the video demo with its script below it:
Welcome! In this presentation I’ll demonstrate how you can conveniently monitor the health and performance of your MySQL servers using MySQL Enterprise Monitor or MEM version 3.0.
When you login, by default you’ll be taken to the overview screen, which you can see here. Now you can use this to get a quick idea of the overall health of your entire monitored infrastructure or just one of a select group. For example, I can select my production replication group, as that’s the group that I’m typically most concerned with. At first I can see the long-term overall availability of the servers in this group.
I can see how many connections are being handled. And this is an easy way to look for big connection spikes in my group. I can see the overall database activity, as measured in DML statements – so Selects, Inserts, Updates, Deletes and so on.
I can see the query response time averages for my group. And please look for the additional video demo where I go into exactly what QRTI is – how it’s calculated and why it’s extremely useful.
I can see what my current problematic MySQL instances are. Problematic meaning that they’re not running or they have unaddressed critical alerts. I can also see what my problematic cause or machines are. Again, meaning that they’re not running or they have unaddressed critical alerts.
And finally, I can see a full list to the unhandled critical events for all the servers in this group. So as you can see, the overview screen is a nice and easy way to see, gauge and monitor the overall health of your monitored assets.
That’s all for this video. Thank you for watching and please be sure to look for our other video demos on MEM 3.0, where I’ll show you how you can dive deeper into the data that’s available here on the overview screen.
