With this Monyog release, we will provide monitoring capabilities for RDS / Aurora OS metrics along with an emphasis on the User Experience in several respects including a number of GUI design details. Additionally, the release adds a number of bug fixes and implements a number of user requests.
Changes as compared to Monyog MySQL Monitor 8.0.4 include:
- It is now possible to get OS metrics from Amazon RDS/Aurora (but not Azure, where interface for same is disabled).
- Added an option to generate a token in Monyog to be used with the MONyog API as an alternative to Monyog user and password.
- Added an option to define a “seconds_behind_master” setting in Replication page determining if the slave should be considered in sync or not. On some environments, slave will rarely be fully in sync and in such cases, the alerting was not really useful before.
- MONyog-bin.pid location on Linux can now be changed from MONyog.ini file.
- Reintroduced the tabular view for Replication overview page. Now, the user can choose between tabular and graphical view.
- Added an option to select the way the server selector should work in Monyog, i.e: same servers across all pages or different across pages
- Seconds behind master could show wrong value in the chart.
- Export as CSV didn’t work for “Locked and Locking Queries” in Real-Time.
- On HDMI and higher resolution monitors, overview page could display distorted.
- Extra columns added from manage columns in Real-Time were getting reset to default set of columns on moving away from the page.
- In Dashboard the value of min/max/avg displayed as 0 if number of points was larger than 10,000, Also, if the chart was exploded, the chart would display empty.
- Some counters did not show values formatted properly.
- In mail alerts for counters in multi-replication monitor group a newline character in subject could cause the mail to display unformatted in some mail clients – including gmail web interface.
- In “long running query” alert there was a bare line feed character (\n) which could cause reading failures in some environments.
- History trend reports will show date as well in the timestamp if report spans more days.
- Collection and Purging interval was not setting properly while editing a UDO.
- Redesigned the interface for adding new servers.
- It is now possible to display the “Replication Overview” page and set auto-refresh interval similar to Monyog before version 7.o. Different users have different preferences here.
- When installing Monyog on a Linux machine with kernel version less than 2.6.32, an error message will now inform that Monyog needs a kernel version or 2.6.32 higher.