Versions Compared

Old Version 3

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 4

changes.mady.by.user Nicolas Rios

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SSL/TLS mail encryption is now supported for mail alerts.
  • Added an option to rebuild Monyog databases. Using this option periodically may result in better performance - including shorter startup time when OS is rebooted. Basically using this option will defragment the database including indexes. It is not possible to provide an 'absolute' advice on how this option should be used. But the larger the databases and the shorter the sample interval the faster there is a chance of fragmentation occurring after a huge amount of INSERTs INSERT´s and DELETEs DELETE´s to the database (note that only with databases files of around 1 GB and larger we have seen the need for this. A 'general' advice could be to execute monthly with large database files).
  • Improved error messages for Query Analyzer.

...

  • The 'query sniffer' can now connect to and retrieve data from a running instance of the MySQL-proxy program used by one or more clients to connect to MySQL. A LUA script for controlling the proxy for use with is provided with this build. With this sniffer option the SHOW FULL PROCESSLIST statement will not be sent and thus use of 'query sniffer' will not put any load on MySQL.
  • SSH connections will now attempt more authentication methods in case the first method attempted failed. This will solve problems reported with tunnneling tunneling to MySQL on FreeBSD that as per default does not support the full range of SSH authentication methods (and possible similar problems).
  • Updated advisors. This is a complete and major revamp of advisors in . It is still in progress (around 80% is finished).
  • Log Analyzer will expose call statements.
  • In Log Analyzer ''Rows Sent' and 'Rows Examined' column will be displayed as KBs/MBs.
  • Connection Details (Connection name, MySQL user, SSH user, SSH tunneling user which are saved in connection details are exposed for customization in Monitors/Advisors. (For instance 'connection name' can be accessed using MONyog.Connections.ConnectionName, 'MySQL user' as MONyog.connections.MySQLUser etc. Please refer documentation for more detailed list of all counters exposed.). Using this option counters can be made specific for specific Monyog connection details. For instance you can have two connections defined to the same server that will display each their set of counters.
  • Monyog now has an ability to fully utilize the caching abilities of modern browsers. Now when refreshing a page where there is no change there will be almost no network traffic generated and the page will refresh almost instantaneously.
  • Monyog is able to read microseconds from proxy and if available in slow query log and will (for readability) show in milliseconds.
  • Sniffer output will now display MAX, first seen time, last seen time, query occurrence %. Also query occurrence % and Lock Time for a query was added to slow query log and query occurrence % for a query was added to general query log displays.
  • Added an option to execute FLUSH STATUS from inside Monyog.

...

  • Adding a server with notification enabled was storing wrong information in the 'connection.data' configuration file. After a restart of the Monyog service the wrong information that was read from that file would cause notifications to stop working. Note that if a connection was configured in 'two steps' where notification settings were added to an existing connection there was no error.
  • Fixed a memory leak occurring with public/private key authentication when connection was unsuccessful (server not available, invalid key pair etc.).
  • The shortcuts installed by Monyog installers now point directly to '127.0.0.1' (and not 'localhost'). This solves an issue with firefox Firefox on Windows Vista where resolution of the URL 'localhost' was very slow.

...

  • Adding a server with notification enabled was storing wrong information in the 'connection.data' configuration file. After a restart of the Monyog service the wrong information that was read from that file would cause notifications to stop working. Note that if a connection was configured in 'two steps' where notification settings were added to an existing connection there was no error.
  • Fixed a memory leak occurring with public/private key authentication when connection was unsuccessful (server not available, invalid key pair etc.).
  • The shortcuts installed by Monyog installers now point directly to '127.0.0.1' (and not 'localhost'). This solves an issue with firefox Firefox on Windows Vista where resolution of the URL 'localhost' was very slow.

...